Skip to content

Executing tests using Test Scheduler

← Worksoft SaaS Self Paced Learning - FHE - Supporting Articles 
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.
 
 Mapping the Worksoft SaaS feature to the Course Context :: Lesson 5 :: Topic 1


1. Executing tests using Test Scheduler
The Test Schduler is already pre-loaded into your Training Project (the same way it is pre-loaded in your Worksoft SaaS Projects) and we will use it to execute the 2 Test Cases simultaneously. As you remember, each Test Case has 2 Testing Context each (1 Chrome/1 Firefox), which means we will see 4 Test Runs executed simultaneously.

In this Sandbox account, we have allotted subscription to allow concurrency for 3 Functional tests on Single browser (Chrome) and 1 Cross-browser test, which means, while executing tests using Runner/Scheduler, you can choose to run one test from Functional High Volume Testing and one test from cross-browser/cross-device.

In order to update the Test data, we will go to 'Business Test Run Details' data file, which is a part of the Test Scheduler and update the Test data of Test Case 1 & Test Case 2. 
     
In the Business Test Run Details, we can specify many preferences:
  • Execution Indicator: You can choose whether to include/exclude the data row for execution
  • Run Definition details: You can update the Testing Context of your preferred Device/OS/Browser combination
  • User Notes: You can choose to update User Notes to maintain a unique Identifier of your Test Runs
  • Cloning feature is also available to easily update the Test data.
In the Test Scripts, we only have the values of Test Case 1. However, in order to execute tests simultaneously, we will update the test data of both the Test Cases in the Business Test Run Details. Then, we will execute the Test Scheduler to trigger the Tests.
    
       
2. Practice
  1. Click Menu and Click 'Data Files'
  2. Click on "Edit" icon to edit "Business TestRuns Details"
  3. Now we will update mandatory details in the below-mentioned column of Row 1. To edit any details, mouse over the cell and click on </> (Premium Editor) Icon Note: Ensure that you are not deleting any Quotes, Brackets, Colon, Edit the details between double-quotes. Execution Indicator Run Definition Details: {
    "testingContextKey": "XXXXXX",
    "runDefinitionStatus": "WIP",
    "runDefinitionNameMnemonicForDeveloper": "Name of Run  ",
    "testingPlatformMnemonicForDeveloper": "true",
    "userNotesForUIDisplay": "Schedule Business Test Runs of smoke test cases on production environment",
    "includeUserDefinedVariablesForWorksoft SaaSAIMLOverrides": "true"
    }
  4. Firstly Change the Execution Indicator to 'Yes' ("Yes"/"No" indicates the need for execution of a particular row).
  5. Now update Run definition Details column as below: Testing_context_key: Open another window -> Go to Run Definition 'Verify the HICC Calculations - State = NJ Zip = 08817 Age = 45 Income = $20000' -> Click on view to see the Testing Context of the respective Run Definition -> Copy the Testing Context Key (with Functional High Volumes Testing Cloud) -> Go to (previous Browser Tab) Data Files screen -> Edit Row 2 -> Go Run Definition column -> Click on Premium Editor -> Paste the Testing Context key ( Ensure testing context key is between double quotes).
  6. Here update the name_mnemonic to 'Verify HICC calculations - State = NJ Zip = 08817 Age = 45 Income = $20000' (This is a unique name given to the row data and will not be displayed anywhere else.
  7. Clone row no 1 with Run Definition 'Verify the HICC Calculations - State = NJ Zip = 08817 Age = 45 Income = $20000'and click Save. Update the below details in the row no 2. Execution Indicator Run Definition Details: {
    "testingContextKey": "XXXXXX",
    "runDefinitionStatus": "WIP",
    "runDefinitionNameMnemonicForDeveloper": "Name of Run Definition ",
    "testingPlatformMnemonicForDeveloper": "true",
    "userNotesForUIDisplay": "Schedule Business Test Runs of smoke test cases on production environment",
    "includeUserDefinedVariablesForWorksoft SaaSAIMLOverrides": "true"
    }  
  8. Update the Run definition Details column as below: Steps to Locate Testing Context Key: Testing_context_key: Open another window -> Navigate to Run Definition 'Verify HICC calculations - State = NY Zip = 10001 Age = 45 Income = $55000' -> Testing Context of the respective Run Definition -> Copy the Testing Context Key (with Functional High Volumes Testing Cloud) -> Go to (previous Browser Tab) Data Files screen -> Edit Row 2 -> Go Run Definition column -> Click on Premium Editor -> Update the Testing Context Key copied
  9. Update the name_mnemonic to 'Verify HICC calculations - State = NY Zip = 10001 Age = 45 Income = $55000'
  10. Update the userNotesForUIDisplay to 'values for State-NY'
  11. All the changes are done. Now Click save
  12. Now click on 'Save & Exit'.
 3. Practice: Updating the Test Cycle Inputs File and Trigger Test Scheduler
  1. Click vertical ellipsis to edit Test Cycle Inputs.
  2. Edit the Test_Cycle_Info
  3. Update the testcycleidentifier as Test Cycle 1
  4. Update the plannedWindowsStartTime:
  5. Update the plannedWindowEndTime:
  6. Click Save and click Save & Exit.
  7. Click Menu and Click Test Cycle
  8. Click ExecuteTest Scheduler.
  9. Select on dropdown to select Test Cycle Inputs
  10. Click Schedule

Please Note:
  • By updating the new values in the Business Test Run Details, the values dynamically override original values in the Test Script, however, the original values are not replaced

     




Feedback and Knowledge Base

(thinking…)