Lesson 5 Topic 1 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 5 :: Topic 1
1. Worksoft SaaS Test Scheduler
When you get started with Worksoft SaaS, you would always schedule your tests manually and monitor the execution physically to check the results. Once these tests are certified, then you might want to schedule them frequently so as to certify for every sprint or build release. Apart from the manual execution, this can also be done using Worksoft SaaS's Test Scheduler, wherein you can scheduler/trigger your tests, maintain them, add/update/override the test data, execute them simultaneously, individually or selectively as per your requirement.
There are many use-cases of Worksoft SaaS Test Scheduler: Let's take an example of an e-commerce website where we need to perform a test to search for multiple items. Whether we want to do this search simultaneously or sequentially, selectively, the Test Scheduler can be used.
In this case, let's say you have a test script called 'Search the Product' and within that Test Script, you have a hardcoded value to search for a book '7 Habits of Highly Effective People'. Now, you want to add more items to your search. So by using the Test Scheduler, we can override the values at the 'Run time' to 'Rich Dad, Poor Dad', Apple iPad Pro 11inch, Epson 8500 Lumens Business Projector' by using the Test Scheduler and all these products will be searched accordingly. Moreover, you can add these Products simultaneously or sequentially using the Test Scheduler. These values will not replace the original test data in the Test Script '7 Habits of Highly Effective People'.
The Test Scheduler can be triggered from Test Cycle Home page. It can be used for any test in any project, as-is since no modifications are required. These Runs are executed with the help of Worksoft SaaS's REST services.
A Test Scheduler is a utility for triggering the Business Test Run Driver. The user needs to initiate only the Runner which in turn will take care of triggering and executing the runs in the Business Test Run Driver as per the schedule configured.
The Runner is also pre-loaded into your projects and is ready to be used as-is or can also be customized to your requirements.
2. QaCONNECT REST Services
Worksoft SaaS's QaCONNECT is a feature that contains a suite of tools for integrating with CI/ALM. (Continuos Integration/Application Lifecycle Management)
REST Services are a part of QaCONNECT that are used to perform various functions like Scheduling/triggering executions remotely.
REST Services are a part of QaCONNECT that are used to perform various functions like Scheduling/triggering executions remotely.
Worksoft SaaS Test Scheduler internally makes heavy use of QaCONNECT REST Services and can perform various functions. The REST API Docs are available here for reference, For each REST call, the "Docs" page provides one or more examples and for each example, sample Request and Response is provided.
3. User Notes
In Worksoft SaaS, User Notes is a feature available to input in the driver data file and helps as an identifier of the Test Run, especially when the data is being overridden.
For Example: If we are overriding the hardcoded value in the Test Script using the Test Scheduler, in the driver data file, we can enter the product that is being overridden with 'iPad Pro 11'
After the test is executed, this information will be visible in the Test Runs Home page, in the form of a triangle on the right-hand corner of the Test Runs column