• Simplified workflow for executing Performance Test Cycles
  

  If you have a subscription that allows you to run performance tests within the Worksoft SaaS platform, this enhancement will offer you significant benefits. So far, when scheduling your performance test cycles using the Worksoft SaaS Test Scheduler component, you had to explicitly request the auto-provisioning of infrastructure necessary for you to run your test cycle that simulates a load of 1000s of concurrent users.

  You were able to do so by checking off the checkbox "Provision infrastructure immediately" within the accordion captioned “Provisioning Infrastructure for the Performance Test Cycles” that shows up as part of the Scheduler workflow.

  You do not have to make that explicit request anymore with this release. The name of the accordion is changed from “Provisioning Infrastructure for the Performance Test Cycles” to “Inputs for Performance Test Cycles” in this release. That accordion does NOT anymore have the checkbox “Provision infrastructure immediately”. Automatically, the necessary infrastructure provisioning will happen for the test cycles.

  You must, however, continue to specify the max concurrency for your performance test cycle as well the list of email addresses to which you want all email notifications related to the scheduling, execution and reporting related to your performance test cycle. The max concurrency you pick, however, has to be equal to or less than the max concurrency supported by your Worksoft SaaS subscription for performance testing.

  Please note that in the enhanced workflow, within the first accordion captioned “Test Cycle Runner Inputs”, you must check off a new checkbox captioned “This is a test cycle for performance testing”. Unless you check this checkbox, you will not be allowed to specify the inputs like max concurrency, etc, in the 3rd accordion.

  Please note that you should not check off the checkbox "This is a test cycle for performance testing" when you schedule test cycles for running your functional and/or cross-platform tests. You should use this checkbox only when scheduling test cycles for your performance tests.

  The screenshots below highlight the key differences in the workflow you experienced so far and the new workflow included in this release.

  
  
  
  
  
  
  

  To learn more about the steps to schedule performance test cycles within your project, click here.

• Separate subscription for Data Validation testing
  

  So far the name of the cloud that you used when executing data validation tests or performance tests was 'Performance Testing cloud' and the name of the subscription was 'Performance Testing'. To clearly differentiate the type of testing that is performed - Data Validation testing or Performance testing, a separate names are included in this release for customers that have a subscription for data validation testing and/or performance testing.

  If you have a subscription that allowed you to execute data validation tests so far, you will now see the new (more aptly) named subscription "Data Validation Testing" and the cloud "Data Validation Testing Cloud".

  If you have a subscription that allowed you to execute performance tests so far, you will NOT see any changes to either the name of the subscription or the name of the cloud.

  
  
  
  
  

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