Versions Compared

Key

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

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

  1.  User should have the QAS - Client installed.

  2. User should be assigned to an existing project.

  3. 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. 

Info

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:

  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.

      image-20240123-114944.pngImage Added
    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.

  8. 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.

Info

If you create an empty object but it is not used in any of the test cases, the Error Toolkit 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 case.