Skip to content

Performance Testing :: Module 3 :: Topic 6.1 :: Test Cycle Scheduling Inputs

This article is a part of the Self-paced Learning Series for the Course: Performance Testing

Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 5 :: Topic 6.1


1. Configure Runner and Driver data file

Now Lets see how to create a Test Cycle and schedule Test Suits using the same:

There are two ways in Worksoft SaaS to create a Test Cycle: -
- Manually using the Worksoft SaaS application
- Creating Test Cycle with Execute Test Scheduler

Manual Creation of Test Cycle is simple and straight forward. We just need to give Test Cycle Name, Description, Planned Window Time etc.. You can refer to the following link for more details on Test Cycle creation manually.

When comes to creating Test Cycle using Test Scheduler, lets see the same now.

Test Scheduler is another feature of Worksoft SaaS, using which we can schedule multiple batches at a time. To schedule any batch we need to have test suite prepared. Here, each test run will have an alphanumeric key called Testing Context using which we can reconginize on which platform the test is scheduled. You can know more about Testing Context from following link.

The test scheduler is already pre-loadded into worksoft SaaS project. To schedule test from our desired project, we need to update the Testing Contexts of our tests in the Data File "Business Test Runs Details". By using the same, we are going to trigger the all the tests simultaneously. You can specify many preferences in the same data file to control your executions. Please refer to following link to know more.

Once the Business Test Runs Details are updated. Please update the Test Cyel Inputs to provide a Name to Test Cycle based on the purpose of testing. To read more about Test Cycle Runner Inputs, please read here.

Feedback and Knowledge Base