Lesson 16 Topic 3 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 16 :: Topic 3
1. Search in Home Page
Similar to the Search options in other Test Scripts, Scenarios, Run Definitions, etc, Test Runs Home Page has a Search button that helps us find specific Test Runs.
There are several fields that can be used independently or in combination with other fields to narrow down the specific Search results. In case you don't have the complete name to fill in the search parameter, partial name Search is also possible.
There are 2 modes of Search available here, Basic and Advanced.
Let's look at some of the basic Search parameters:
1. Test Cycle Identifier: This is the easiest search parameter that gives specific results as every Test Cycle has an Identifier that is unique.
2. Batch Label: An advanced concept used while scheduling tests using QaCONNECT and/or Runner & Scheduler. You may have a requirement wherein a certain set of tests should be executed in specific sequence. To accomplish that you can use Batch Label while scheduling tests using QaCONNECT. What it does is to allow for you to group different tests under different batch labels and then define a dependency between these batches. If you have attempted such executions, this field will help you in searching for a specific set of tests based on Test Cycle Identifier and Batch Label.
3. Don't show runs tagged to "Do not show in report(s)" Label: This is a system defined label and Runs that are tagged to label "Do not show in report(s)" will not show up in the Reports.
There will be cases when some Test Runs fail either because of some test data issues and/or automation or flakiness issues. In these cases most often than not, you end of executing the tests again. In such a scenario, you will opt not to show the original failed test runs in the final report as it is not needed. Using this label, you can explicitly choose to hide such test runs from the reports.
By default these are hidden in Test Runs home page as well. If you want to explicitly see these test runs, you can turn the checkbox ON.
4. User Notes: User Notes is a free text field that can be used to provide additional information while triggering runs. This is available at each run level and can be used to differentiate runs when the same run definition is used for multiple tests.
One common use case when User Notes come handy is when you use the same test case (Run Definition) to execute for two different users like guest or registered user on an e-commerce site. For you to quickly identify which test run is what, User Notes can be used to add the information.
The text can be seen in the Test Runs Home page
5. Instructions Pass: This is a helpful option if you want to see a list of Test Runs with a specific % of Instructions that were passed/failed.
6. Scheduling Source: Here we need to select the source that was used to trigger the run. For e.g if a run was triggered from Worksoft SaaS application, we will select SAAS as the source, If the run was scheduled using QaCONNECT Rest API services then we will select QaCONNECT, and if a run is failed run was triggered by Worksoft AI/ML we will select Worksoft AI/ML