• Test Cycle Report Generation - Ability to generate multiple reports in parallel
  

  With this release, you will be able to request the generation of test cycle outcome reports for multiple test cycles simultaneously. Depending on the configuration of the the report hierarchy within your project as set by your project lead, the multiple requests will either get processed in parallel or sequentially.

  If the configuration of the the report hierarchy is such that the "test cycle" is the root node, then the test cycle report generation requests that you submit will be processed in "parallel".

  If the configuration of the the report hierarchy is such that the "test cycle" is NOT the root node and something else like the "environment" is the root node, then the test cycle report generation requests that you submit will be processed "sequentially".

  Irrespective of the configuration of the test cycle reports report hierarchy within your project, all your requests for test cycle report generation will be "queued" up. Depending on the root node being the "test cycle" (or not) the queued up requests will be processed either in parallel or sequentially.

  Click here to learn more.

  
  
• Ability to view and copy the Selenium Cloud Platforms Access Keys for use within Appium Inspector for Native Mobile Automation
  

  You will now be able to copy to clipboard the username and the access key for the external Selenium Cloud Providers like Browser Stack and Saucelabs from within the View and Edit Selenium Cloud Platforms screens. You will then be able use the copied username and access key to connect to the Cloud Platform from within "Appium Inspector" that you use to build and maintain the test automation for your native mobile apps.

  

  Click here to learn more about this feature.

  
  
• New Commands that allow Test Scripts to Create Datasets from JSON and XML Files hosted within the Files module and to store the contents of a file within the "Files" module into a Variable
  

  This release offers you 3 additional powerful commands to read the content of Text, JSON or XML files stored within the "Files" module of your project to populate Variables or create Datasets that then can be used within your automated tests.

  • ddCreateDataSetFromXmlFile: This command is used to create a DataSet from an XML File that is present within the "Files" module in the project. The command takes as input two parameters (a) In the "Target" field, the "XML Filename" and (b) In the "Value" field a DataSet name. This dataset must have been created using the "ddCreateDataSet" command within a test instruction that is executed prior to (ahead of) the test instruction which contains the "ddCreateDataSetFromXMLFile" command and in the same test. For more details, click here.
  
  
  • ddCreateDataSetFromJsonFile:This command is used to create a DataSet from an JSON File that is present within the "Files" module in the project. The command takes as input two parameters (a) In the "Target" field, the "XML Filename" and (b) In the "Value" field a DataSet name. This dataset must have been created using the "ddCreateDataSet" command within a test instruction that is executed prior to (ahead of) the test instruction which contains the "ddCreateDataSetFromJsonFile" command and in the same test. For more details, click here.
  
  
  • storeContentFromFile:This command is used to "store" the contents of a "file" of txt, json and xml file formats present within the "Files" module in the project. The command takes as input two parameters (a) In the "Target" field, the "Filename" and (b) In the "Value" field a Variable name into which the file contents will be stored into. For more details, click here
  
  

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