Skip to content

Cloning Test Scripts, Scenarios & Run Definitions

← 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 4 :: Topic 1


1. Review Manual Test Case 2
For the purpose of Cloning, we will look at another Test Case where the Test data is different. 

Refer to TC #002 from the Test Case Repository

     
2. Cloning Entities like Test Scripts, Scenarios & Run Definitions
As you can see that Test Case 2 is similar to Test Case 1, in terms of functionality and the only difference is the Test data, hence we can use the cloning feature to clone the entities of Test Case 1.
  • The benefit of cloning the Test Scripts is that the instructions (Test logic) will be copied and will operate on the new test data. 
  • The benefit of cloning the Scenario is that the predecessor Scenario will be copied into the new cloned Scenario. 
  • The benefit of cloning the Run Definition is that the Testing Context will be copied into the new cloned Run Definition.
                              
     
After cloning the entities, we will have to follow a few steps to update them as per Test Case 2
  • In the cloned Test Scripts, we will need to update the Test data of the Test Case 2. 
  • In the cloned Scenario, we will need to remove the Test Scripts of Test Case 1 and replace it with Test Scripts of Test Case 2.
  • In the cloned Run Definition, we will need to remove the Scenario of Test Case 1 and replace it with Scenario of Test Case 2.    
             
3. Practice:

Cloning Test Scripts:
  1. Click Menu and Click Test Scripts.
  2. Click Vertical ellipsis in Actions Column and click on Clone to copy the 'Enter & Submit Inputs for HICC - State = NJ Zip = 08817 Age = 45 Income = $20000'
  3. Change the Test Script name to 'Enter & Submit Inputs for HICC - State = NY Zip = 10001 Age = 45 Income = $55000'
  4. Scroll to the instructions and replace the Annual_Income value with 55000, Zipcode value with 10001 
  5. Click on Save as WIP and Exit.

Clone another Test script
  1. Click Menu and Click Test Scenarios.
  2. Click Vertical ellipsis and click clone the 'Verify Results of the HICC - State = NJ Zip = 08817 Age = 45 Income = $20000'
  3. Change the Test Script name to 'Verify Results of the HICC - State = NY Zip = 10001 Age = 45 Income = $55000'
  4. Double Click and expand first instruction and replace value by "You are not eligible for a subsidy." and Click save"
  5. Double Click and expand second instruction and replace value by $6,159 and Click Save
  6. Double Click and expand third instruction and replace penalty value by $550 and Click save
  7. Click "Save and Exit"
Cloning Scenarios:  
  1. Click Menu and Click Test Scenario. 
  2. Click Vertical ellipsis and click Clone to clone 'Perform data inputs and verify results for HICC - State = NJ Zip = 08817 Age = 45 Income = $20000'.
  3. Change the Scenario name to 'Perform data inputs and verify results for HICC - State = NY Zip = 10001 Age = 45 Income = $55000'.
  4. Delete the existing Test Scripts
  5. Assembling the Test Scripts with NY data
  6. Scroll up and Click Save as WIP and Exit
Cloning Run Definitions (RD):
  1. Click Menu and click Run Definition.  
  2. In the Actions Column I will click vertical ellipsis and then Click on Clone to Clone the Run Definition Verify HICC Calculations - State = NJ Zip = 08817 Age = 45 Income = $20000'.
  3. Change the RD name to 'Verify HICC calculations - State = NY Zip = 10001 Age = 45 Income = $55000'.
  4. Delete the existing Scenario.
  5. Assemble the Scenario with NY data (with Predecessor and Successor Scenario)
  6. Click on 'Continue'
  7. Proceed to testing context, Select Testing Context with Production environment and execute the test.
 
Please Note:
  • The Entity Names suggested are only for the purpose of this Training. As a best practice, we do not recommend lengthy names, adding sequence numbers or test data in the name.


     

Feedback and Knowledge Base

(thinking…)