Commands for creation and assignment of 'Labels'
In Worksoft SaaS, 'Labels' play a very critical role not only during and the creation and maintenance but also during the execution and triage of automated tests. For example, during the creation and maintenance, the labels can be used to build and maintain traceability of automated tests to their manual test counterparts or to the application functionality/features or software requirements. They also facilitate the users within a project or organization to find the automated tests or their component entities (scripts, scenarios, run definitions, data definitions, data files, etc) easily by tapping into the search based on the labels. When(ever) the automated tests are executed, if there were any unexpected outcomes/failures, labels also come handy in allowing you to document the root cause for such failures and to access various analytics that are available that summarize and report the test outcomes by root cause.
Labels can be created and maintained manually as well through the automated tests during their run time execution.
Worksoft SaaS offers several commands that allow your automated tests in execution to create labels and to assign labels to tests.
Here are some use cases where you can benefit from these commands:
- Assign labels dynamically at the beginning of execution of a test so that the context of the test is accurately recorded/assigned. For example, may be you want to assign the testing purpose or automation state. If your automated test maps to more than one manual test case or more than one manual test case scenario and depending on the scope of your automated test at run time, your test can assign the appropriate labels.
- If exceptions or errors (or failures) occur within an automated test at run time, your tests can assign the right root cause for failure dynamically based on the exception handling logic implemented within your automated tests.
The table(s) below list the commands in the ascending alphabetic order within each category along with a brief description of the purpose behind the command. By clicking on the hyperlinked command name in the table(s) below, you can review more detailed information about a specific command that includes the syntax for you to follow when using the commands. Please note that these commands (constructs) are supported within Worksoft SaaS application (Edit Test Script screen) only and NOT supported in QaSCRIBE test authoring tool.
| Command | Purpose |
|---|---|
| setLabelsWithCreationEnabled | This command is used to create labels and assign the label to a specific "test run" that is in the scope of the automated test in execution You can create root level (top level) labels as well as child labels. This command comes in handy in case you do NOT want to predefine root causes for failure upfront but want them dynamically created based on the negatives outcomes that tests experience at dynamic run time. Since it is automation that is creating new labels, the disadvantage with using this command, however, is that you may end up seeing way too many root cause of failure labels that makes it difficult to reap any value when you access the various analytical reports that are available that summarize outcomes by root cause. Having said, if you take extra precaution to prevent the creation of a high number of unmanageable root cause labels, this command can turn out to offer significant value. |
| setLabelsWithoutCreationEnabled | This command is used to only "assign" one or more label(s), that "already exist" at the root (or any other level)
to a specific "test run" that is in the scope of the automated test in execution. This command will NOT create labels that do not exist already. If you want a project leads or managers (or specific individuals) within a project to 'define' the master list of root cause for failures and the automated scripts have to assign (at their run time) only from that list, then this is the command you want to use. |