Page Comparison

...

1. Login to QAS - Client.

2. Access Develop from left navigation to view Test Explorer screen.

   1. On the Explorer section, you can view existing Test Scenarios.

3. Click the Expand option on a test scenario, where you can view all its test cases.

4. Open the test case for which you want to view the error information.

5. Click Error Toolkit icon at the bottom-left corner of the Test Explorer screen.

6. Clicking Error Toolkit icon will open the Error Toolkit explorer.

7. 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. Tasks: 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. Objects: On the Objects 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 Actions: On 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.

8. The Test Cases, Tasks, Objects, and Custom Actions tabs consists of the following columns:

   1. Serial Number: Lists the number of rows.

   2. Type of Errors:

      • This column will display all the errors related to test cases, tasks, objects, and custom actions that are used in test cases. Errors for the tasks, objects, and custom actions that are not used in the test cases are not reflected in the Test Cases tab.

      • You can expand or collapse the Types of Errors using the Expand (+) and Collapse (-) options.

      • By single-clicking on the type of error, you are redirect to the test editor and the row with the error is highlighted in blue.

   3. Sync Testcases: You can sync test cases by clicking Sync Testcases.

   4. Search: You can use this field to search type of errors.

   5. Line Number: This column displays the Editor test case step or task line number where error has occurred. If user double-clicks on the line number, then the respective line gets highlighted in blue on develop section.

   6. No of Errors: The total number of errors for a respective test case, task, object, or custom action is displayed in red in this column.

   7. Updated By: The name of the user who has created or updated the test case is displayed in this column.

   8. Updated On: The date and time when the test case is last updated is displayed in this column.

9. Refresh: In case of multi-user, if user1 made changes then user2 will be notified by a Red Dot near the refresh Refresh button. If you want to apply the changes made by user1, click Refresh.
   Also, if user1 is making changes to a test case or a task, it will be locked for User2 (or any other users) and you will not be able to update or edit it. This again will be notified to user2 with a Red Dot near Refresh icon.

...