Versions Compared

Old Version 3

changes.mady.by.user Shruti Agrawal

Saved on

compared with

New Version 4

changes.mady.by.user Shruti Agrawal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

If you create an empty object but it is not used in any of the test cases, the respective error will only be visible on the object tab in the Error Toolkit.

Similarly, if the created custom action has an error and if it is not used in the test case, the error will not reflect an error for it.Similarly, the error will not be reflected for a custom action if it is not used in the test caseonly be reflected in the custom action tab.

Types of Error

Error Type

Description

Test case step is empty. Select an action.

This error will occur if a test case step is added without adding objects or actions.

Task step is empty. Select an action.

This error will occur if a task step is added without adding objects or actions.

  • Add an Action for the object in the test case step.

  • Add an Action for the object in the task step.

If any action is not added for an object, the appropriate error will be displayed in the error toolkit.

Add Locator Type and value for the object.

If the created object does not include any locator type and value, the Error Toolkit will show the appropriate empty object error in the object tab.

  • Empty object used in test case step. Set locator type and value in the object.

  • Empty object used int task step. Set locator type value in the object.

If the empty object is used in any test case or task, the Error Toolkit will show the appropriate empty object error in the Test Case and Task tabs.

  • Deleted object used in test case step.

  • Deleted object used in task step.

In the multi-user scenario, if the object used in a test case or task has been removed from the object repository by a user, the other users will get this error.

Custom Action Class file is missing. Reopen Eclipse from Custom Action Toolkit to generate the class file.

If the ".class" file is missing, you will be notified that the custom action has an error.

  • Deleted custom action used in test case step. 

  • Deleted custom action used in task step.

This error message will be displayed if a deleted custom action is used in a test case or task. [Multi-user scenario]

  1. Include conditional expression in the Conditional Structure. [Mention If Else]

  2. Include conditional expression in the Conditional Structure of a test case condition.

  3. Include conditional expression in the Conditional Structure of a task step condition.

If the conditional blocks introduced with blank expression, these error messages will be displayed.

Invalid conditional expression in IF conditional structure of a testcase condition. Check if you have used assignment (eg:{a}={b}) for comparison. Assignment operator is not allowed in expression. please use comparator operator (==).

If an assignment operator is added instead of the comparison operator, this error message will be displayed.

Add Parameter value (for Action) to test data.
Add parameter value to test data or add $NULL$ for empty value.

This error message will be displayed if the action added for the test case or task has a clear parameter text box on the test data.

Parameter name mismatch between test data and test case.

If different parameters are added for the same action on test data and test case, this message will be displayed.