Error Toolkit

Qualitia Automation Studio (QAS) enables you to rectify the errors in the Test Case using the Error Toolkit. Error toolkit is an information-based toolkit, which cannot be edited, deleted, or modified.

📚Prerequisites

User should have the QAS - Client installed.
User should be assigned to an existing project.
A test scenario should exist.

🔑Privileges

User should have the below privileges to:

Import Feature: Import test cases or other project elements.
Manage Custom Action Code: Oversee the custom action scripts in projects.
Manage Objects: Control the objects within the testing environment.
Manage Scenarios: Control the scenarios within test suites.
Synchronize Objects: Keep test objects synchronized.
Test Development: Create and update test cases.

You can save the Test Case with an error but cannot execute.

You cannot execute a test case with an empty object. QAS - Client will show an error for an empty object. It will show a red box around the line number and a red-doted underline for Object, Action, Test Case Name, and Scenario Name.

To check the errors in the test case:

Login to QAS - Client.
Access Develop from left navigation to view Test Explorer screen.
1. On the Explorer section, you can view existing Test Scenarios.
Click the Expand option on a test scenario, where you can view all its test cases.
Open the test case for which you want to view the error information.
Click Error Toolkit icon at the bottom-left corner of the Test Explorer screen.
Clicking Error Toolkit icon will open the Error Toolkit explorer.
On the Error Toolkit explorer, you will see five different tabs.
1. Current Test Case: It will show errors for the selected test case. If there are no errors, it will display a message There is no error in the Current Test Case. In case of an error, QAS will reflect a related message. For example, if a test case step is empty, it will display Test case step is empty. Select an action.
2. Test Cases: This field shows the count of test cases with error for a scenario. For example, if a project scenario consists of three test cases out of which two have errors, so the count shown will be Test Cases (2). Under this tab, you can view information such as the Serial Number, Type of Errors with a search option, Line Number, No of Errors, Updated By, and Updated On.
  - Type of Errors: This will show all test case names with hierarchy of errors. By double-clicking on the error, you can load the test case in the Test Case explorer and the error will be highlighted.
3. Task: This field shows the count of tasks with error. Under this tab, you can view information such as the Serial Number, Type of Errors with a search option, Line Number, No of Errors, Updated By, and Updated On.
  - Type of Errors: This will show all task names with hierarchy of errors. By double-clicking on the error, you can load the task in the Task explorer and the error will be highlighted.
4. Object: In the Object tab, you will see an error if you have an empty object. You will see a message Add locator type and value for the object. By double-clicking on the error, you can open the Object explorer and edit the object.
5. Custom Action: In this tab, you will see errors related to the custom action. By double-clicking on the error, you can open Edit Custom Action screen and edit the custom action.
Refresh: In case of multi-user, if user1 made changes then user2 will be notified by a Red Dot near the refresh button. If you want to apply the changes made by user1, click Refresh.

Once you resolve the error by making the suggested changes, the errors will be automatically gone from the Error Toolkit.

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 only 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]
Include conditional expression in the Conditional Structure. [Mention If Else] Include conditional expression in the Conditional Structure of a test case condition. 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.