Skip to content

Release Notes - 08 April 2019

New Features available for you to benefit from:

Included in this release are the following features:

  • Productivity Improvement: Provision to search within the test instructions of a test script. 

    Earlier, there is no provision to search for a command/target/value within the test script page and it would be a tedious job for you to search for a specific locator/value from the test script. From this release, you can enjoy this benefit by performing the search within the test script using the search control and upon clicking you can see the test script name getting hidden and the search grid getting displayed simultaneously as shown below


  • For more information on how to start using this, please click here.

  • New Commands: Commands to get the JSON and XML data during the Test Execution.

    Two new commands are introduced in this release, these are part of 'Commands for Array Creation and Manipulation'. These commands help in retrieving the JSON and XML data.

  • ddCreateDatasetFromJsonObject
  • ddCreateDatasetFromXmlDocument

  • To know more about commands for Array Creation and Manipulation, click here.

    These new commands allow you to pass the JSON/XML as the input and create datafiles which can be used in further execution of the run.

  • Productivity Improvement: Change in the implementation of finding the element having multiple locators.

    Earlier, while finding an Element it always starts finding the element using the locators in the same order they were added. In xxxVisible commands, if the user is adding a locator that is available but not visible on the page and the second locator is the correct locator that the user is trying to validate, it always gets the element of the first locator and the command fails even though it has the correct second locator.

    With this implementation, it starts finding the element from the next locator and iterates all the elements. This way it would be able to iterate through all the locators even though the element is found and the next operation that was performed on that element fails.

    Share your ideas – Help us improve Worksoft SaaS!

    We could not have gotten Worksoft SaaS to where it is without some brilliant ideas from all of you. Keep the suggestions and ideas for improvement flowing!

    To submit an idea or vote on some of the features requested by other customers, click here



Feedback and Knowledge Base