Included in this release are the following features:

• Major Enhancements to the screens that you use to View/Edit Test Scripts
  

We are excited to share with you that, as part of this release, there is a major overhaul to how you maintain test scripts within the Worksoft SaaS application (specifically the screen you use to edit or view a test script). Numerous user interface/workflow and productivity improvements are packed in this release.

We strongly recommend that you get familiarized with all the new user interface design and the various new features offered by clicking here.

• Ability to 'Lock' Test Scripts from edit by others
  

The Script Library for each project is shared across multiple people that may share the responsibility of creating and maintaining the scripts within the library. If your project involves more than one person that is responsible for maintaining the test scripts, it is likely that more than one person can simultaneously get into the 'edit' mode of a test script and start making changes unaware that someone else on their team has already started making changes to the same script. This could potentially lead to accidental overwriting of changes done by one person by a person that saved the changes after the first person saved his/her changes to that test script.

To avoid such a situation, you can 'lock' a script from edit by others. If you have plans of editing a test script soon, you should make use of this feature. However, do not keep it locked from edit by others for long periods of time, especially when you are done with your changes and saved them. Locking scripts from edit by others when you don't have anything else to changes in those locked test scripts can inconvenience others that may want to make changes to the same test script. Please be careful when you use this feature.
To learn how to start using this feature, click here.



• Quick Reference Guide for Test Scripts module 'Inline' within the Worksoft SaaS app
  

For the test scripts module, in addition to the rich documentation in our Knowledge Base, a 'Quick Reference Guide' is natively available now for you to use within the Worksoft SaaS application.
This Quick Reference Guide will help you find information on how to use a specific feature or a high level description of the features. To access it, just click on the little light bulb icon right next to the 'View Test Script' or the 'Edit Test Script' screens.

• New Commands & QaCONNECT REST services: Each test within a test cycle can write data to 'clipboards' that can later be consolidated at the test cycle into 'data files' or 'analytical reports' 

Three new commands and a QaCONNECT web service are now available for you to use to get significant value in case you have business needs like described below. A business case from eCommerce customer is illustrated below as an example. However, the new commands and web service will also be beneficial to customers in other verticals and domains.
Let us assume that you want the automated tests to verify if the product pages (PDP as they usually called) are showing the correct content and pricing for all the products in the catalog that had some changes deployed as part of a release done into a specific environment (production or staging). The number of products (or styles and colors of those products) may be in the tens of thousands depending on the size of your product catalog. You'd have created a single run definition that contains the test scripts that perform all the checks for content and pricing that you wanted to get done. Using the powerful data-driven testing support that Worksoft SaaS offers, most likely you'd be running the same run definitions hundreds or thousands of times, each time feeding in a different list of products. You'd do that to be able to do checks on different products in parallel so that the time window you need to finish the checks on all the products can be as small as possible. But in this, you or your business users typically expect a single report that includes the consolidates all variances found by all the automated tests. They would not prefer to have to deal with as many mini-reports as there were test runs you executed within a single test cycle. 

Now, to accomplish this, Worksoft SaaS offers you 3 powerful commands and a new QaCONNECT web service that make it easy for your provide your business users (or other stakeholders) a single consolidated report that meets their expectations and do so rapidly and without too much effort.

To make use of this new feature, the first thing for you to do is to use the new command 'ddPersistDatasetToTestCycleClipboard' within the test script(s) that is(are) part of the run definition that does all the checks on your PDP page to write the variances found (or any other information... it does not have to be errors only) to what we call a test run level 'clipboard' (some sort of a temporary storage). Assuming you execute hundreds or thousands of test runs of the same run definition each time feeding in a different set of products, as many test run clipboards would have accumulated some information that is of interest to you and your business. 

The next obvious step is for you to get a single consolidated output that accumulates the information from all the hundreds or thousands of test run level clipboards. Worksoft SaaS allows you to get the consolidated output to appear either as a 'data file' or an 'analytical report'. The former will appear automatically within your project's 'Data Files' module whereas the latter will appear as read-only 'report' within your project's 'Analytics' module within the Worksoft SaaS application. If you choose to get the consolidated output as a 'Data File', you have an advantage that the contents of that data file can be used to drive other test runs involving other run definitions in your project. However, please be aware that if you choose the data file option, Worksoft SaaS limits the size of the data file to a max of 5000 rows. If the consolidation of information from all your run level clipboards within a test cycle does not exceed 5000 rows, then the consolidation process will create a data file with 100% of information from those clipboards. If the consolidation process creates more than 5000 rows of information, then only the top 5000 rows of information will be written into the data file. Such a restriction does not exist if you were to choose the 'analytic report' as the output format.

You may now ask 'How then can I get the consolidated output from the information that is in all my test run level clipboards?". Very easy. Make use of one of two ways:

1. Create another run definition that test script(s) that make use of either of the commands 'ddCreateDataFileFromTestCycleClipboards' or 'ddCreateAnalyticsReportFileFromTestCycleClipboards'. The first command will create a data file. The second will create an analytical report.


2. Call the web service within the Worksoft SaaS QaCONNECT REST API  (https://www.eureqatest.com/.../executions/create-consolidated-output-from-clipboards).



In either case, the data file or the report will be named as "testCycleIdentifier_nameOfDataDefinitionOfDataset_dateTimestamp", where "dataTimestamp" is a unique identifier that is of the format "ddmmyyhhmmssSSS" [example: "31072018061327021" that represents 31st day of 7th month of year 2018 at 06 hrs 13 minutes 27 seconds and 21 milliseconds].

For more details on this feature, click here.

• New Browser/Device Platforms supported in Worksoft SaaS:

Type	Browser/Version	Operating System/Version	Device/Model
Newly Supported	Chrome 68	OS  X Sierra (10.13) OS  X Sierra (10.12) OS X El  Capitan(10.11)	Desktop
Newly Supported	Chrome 68	Window 10 Windows 8 Windows 8.1 Windows 7	Desktop