Included in this release are the following features:

• Commands that support the creation and assignment of 'Labels' from within your automated tests
  

In this release, we are introducing 2 new commands that will support the assignment of labels (with optional creation) from within your automated tests during their run-time execution. So far, the creation of labels had to be done manually within the labels management screen within the Worksoft SaaS application, The assignment of labels was allowed to be done, so far, either as part of the scheduling of the tests within a test cycle (using the QaCONNECT REST API) or by assigning labels to the 'Test Cycle' when the test cycle is created (either within the Worksoft SaaS application user interface/workflow OR using the QaCONNECT REST API) OR by assigning the labels statically to the various automation entities like test scripts, scenarios, run definitions, etc., The assignment of root cause of failure labels, so far, had to be done either manually on the 'test execution results' screen within the Worksoft SaaS application OR using the QaCONNECT REST API.

With this release, you can also assign labels from within your automated tests by using new commands that are being offered to you. 

• setLabelsWithCreationEnabled
• setLablesWithoutCreationEnabled


To know more about these commands click here

• Commands that support Logging and Reporting Application Performance
  

If you want to log the performance timing or response times of the components within your application, from within your automated tests, this release offers you many powerful commands and approaches.

You can use this new set of commands to log the timing metrics about the performance of your application under test, from within your automated tests during their run-time execution. 


Sometimes you may want to log the cumulative execution time of a block of test instructions within your test as a key event's timing metric you want to report on. Some other times, you may want to get key application performance related timing metric (like page load time, DOM load time, etc., ) using JavaScript functions (using libraries like Resource Timing API that many browsers natively support, that you can get using runScript command within Worksoft SaaS) or using the Worksoft SaaS supported functions by tapping into the 'runEventTimingFunction' command and log the response from those functions as your key event timing metric that you want to report on. In the same test, Worksoft SaaS allows you to log some key event timings using the former approach described above and some other key event timing metrics using the latter approach.

To know more about these commands click here


• New Commands that support creating 'Aggregations' and 'Summaries' for the test outcomes within 'Test Cycles' or 'Test Runs'
  

This is yet another very powerful feature that is available for you to tap into if you want to create aggregates (like Sum, Average, Max, Min, etc) on data that is available within the 'Data Sets' in the scope of your automated test's run-time (OR the 'Data Files' within your project) and persist those aggregates back into other Data Sets within the run-time of your test OR the Data Files within your project.

The great thing about the new sets of commands, listed below, that allow you to accomplish that is you can use SQL that you are comfortable and familiar with within the commands.

• createAggregationsOnDataset
• createAggregationsOnDataFile

To know more about these commands click here.