Skip to content

Release Notes - 15 April 2019

From this release, you can see the test script name shown within the error message as shown below:
New Features available for you to benefit from:

Included in this release are the following features:

  • Productivity Improvement: Provision to set response time units for logging and reporting on 'Application Performance' commands. 

    Earlier, there is no provision to specify the time units for the 'Application Performance' commands. By default, the time units are specified in milliseconds. From this release, you can set the response time units in Hours/Minutes/Seconds/Milliseconds.

    For more information on how to start using these commands, please click here.

  • New Command:: ddPersistDatasetToDataFileTemporary 

    A new command is introduced in this release, this is part of 'Commands for Array Creation and Manipulation'. This command helps in creating a temporary data file and use the same in the further execution of the run.

    ddPersistDatasetToDataFileTemporary

    This command is similar to ddPersistDatasetToDataFile except that, this new command will not save the data file. The data file created with this command can be used only in the same run.

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

  • Productivity Improvement: Enhancement to the error message shown for the test runs failed with 'Array Creation and Manipulation commands'. 

    When any of your test runs fails with 'Array Creation and Manipulation commands', then you have to search the entire list of test scripts included in the test run to make the necessary changes which is a tedious process as the test script name is not mentioned in the error message.

    From this release, you can see the test script name shown within the error message as shown below:

    "For one or more Instructions within the Test Script(s) "Create Dataset and persist to Datafile" that use the "ddGetCellValueByIndex | ddSetCellValueByName" command(s), the Dataset name provided in the ''Target'' field does NOT exist in the scope of the Run Definition/Test Scenario"

    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