Worksoft SaaS platform allows for running performance tests on customer AUTs. You can launch user sessions from multiples of 10s to multiples of 1000’s depending on the subscription you have purchased with Worksoft SaaS.

When functional tests or regression tests are performed, SaaS platform takes care of launching required infrastructure. But given the variety that one can expect to see with performance tests, you are expected to provide additional information while scheduling these cycles and also wait for some additional time (10-20 mins) for the infrastructure to be provisioned. If you schedule test cycle using "Schedule Now" platform will add some time lag to allow for itself to launch the environment.

When you have Performance Testing as part of your contract with Worksoft, you would see an additional checkbox in the first accordion along with third accordion as shown in the below picture.

By default the third accordion shows in  disabled  state until you click on the third checkbox i.e. "This is a test cycle for performance testing". When you are scheduling a performance test cycle, you need to check the checkbox to enable the "Inputs for Performance Test Cycles" accordion to provide additional inputs required for Performance test cycle

Inputs for Performance Test Cycles

There are two inputs needed i.e. Concurrency (mandatory) & Email Recipient (optional).

1. Concurrency

In the drop down you will see multiples of 100. This is nothing but the number of user sessions you intend to scale to during the test cycle. Note that max value shown in the dropdown is limited based on your subscription for performance testing.

You choose the value that you intend use in the cycle.

2. Email Recipients

SaaS platform will send emails once in the following instances

• When provisioning of environment starts
• When provisioning of environment completes (successfully or failed)
• When test cycle starts
• When test cycle complete
• When report generation starts
• When report generated complete
• When environment is de-commissioned

You can provide more than one email recipient (follow the process listed below this field.) Note that you need to provide at a minimum one recipient before you can schedule the cycle.

Points to Note

• When you use "Schedule now" option to schedule the test cycle, it actually would get scheduled to start x mins into the future from the time you submit the request. This is to ensure environment is provisioned before the tests start and "x" varies based on the concurrency you specified. This can be between 10-20 mins the higher the concurrency the more time is given for the environment to provision.

• If you want to run more than one test cycle, you can do that by adding more than one entry in Test Cycle Inputs file that you use for scheduling the tests.
  

• Once the test cycle completes, environment would be decommissioned automatically. It also gets de-commissioned automatically when any of the following conditions are met


• When more than 10% of runs fail with pre-processing errors
• When environment is up for more than 3 hours
• When cycle is completed, and reports are generated successfully