Skip to content

Using Data File Overrides in the 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 7:: Topic 2


1. Executing tests using Data Files
In the previous Lesson, we parameterized Test Scripts to UDV's and passed the test data of Test Case 1 & 2 from the UDV after each Test Case execution.

Now, we will parameterize the values of Test Script to Data Definitions and pass the test data of Test Cases 1, 2 & 3 from the Data File after each Test Case execution.

Here, we will create a Data Definition (which is a pre-requisite to creating your Data Files), it can be created Manually or by Bulk import (after designing the structure for multiple Data Definitions)

Once the Data Definition is ready, we can download the Data Definitions file that acts as a template where the Data Definition attributes act as column headers and can be used to populate the test data accordingly.
       
2. Practice     
  1. Click Menu and Click 'Data Files'
  2. Click on "Edit" icon to edit "Business TestRuns Details" 
  3. Now clone Previous row and click on Save icon in action column to Create Row 7.
Now we will update mandatory details in below-mentioned column of Row 7. 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"
}
data_file_overrides
     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:

Steps to find Testing Context Key: Open another window -> Go to Run Definition 'Enter & Submit Inputs for HICC (Parameterized with Data Attributes)' -> 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 7 -> 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 ''Enter & Submit Inputs for HICC (Parameterized with Data Attributes)' (This is a unique name given to the row data and will not be displayed anywhere else)
     7. Update the user_notes_override to 'Values for State-NJ'.
     8. Now we will data_file_override, Navigate to data_file_override column and click on Premium Editor and Paste below-mentioned Json:

[{   "currentDataFileName": "HICC - 1 Zip code or state in 3 States",   "currentDataFileStatus": "WIP",   "replacementDataFileName": "HICC - 2 Zip codes in NJ",   "replacementDataFileStatus": "WIP"}]

     9. Clone Previous row with Run Definition 'Enter & Submit Inputs for HICC (Parameterized with Data Attributes)'' and click Save. Update the below details in the row no 8

Now we will update mandatory details in below-mentioned column of Row 8. To edit any details, mouse over the cell and click on </> (Premium Editor) Icon.

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"
}
data_file_overrides

     10. Update the Run definition Details column as below:

Steps to Locate Testing Context Key:

    testing_context_key: Open another window -> I am going to Run Definition 'Verify HICC calculations (Data-driven by UDVs) -> Clicking on view to see the Testing Context of the respective Run Definition -> Copying the Testing Context Key (with Functional High Volumes Testing Cloud) -> Go to (previous Browser Tab) Data Files screen -> Edit Row 8 -> Go Run Definition column -> Click on Premium Editor -> Update the Testing Context Key copied

      11. Update the name_mnemonic to 'Enter & Submit Inputs for HICC (Parameterized with Data Attributes)'
      12 Update the user_notes_override to 'values for State-NY'
      13 Now we will data_file_override, Navigate to UDV column and click on Premium Editor and Paste below mentioned Json:

[{   "currentDataFileName": "HICC - 1 Zip code or state in 3 States",   "currentDataFileStatus": "WIP",   "replacementDataFileName": "HICC - 2 Zip codes in NY",   "replacementDataFileStatus": "WIP"}]

      14 Now clone Previous row and click on Save icon in action column to Create Row 9.

Now we will update mandatory details in below mentioned column of Row 9. 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"
}
data_file_overrides

       14 Firstly Change the Execution Indicator to 'Yes' ("Yes"/"No" indicates the need for execution of a particular row).
       15 Now update Run definition Details column as below:

Testing Context key: Open another window -> Go to Run Definition 'Enter & Submit Inputs for HICC (Parameterized with Data Attributes)' -> 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 6 -> Go Run Definition column -> Click on Premium Editor -> Paste the Testing Context key ( Ensure testing context key is between double quotes).

        16 Here update the name_mnemonic to 'Enter & Submit Inputs for HICC (Parameterized with Data Attributes)' (This is a unique name given to the row data and will not be displayed anywhere else)

         17 Update the user_notes_override to 'Values for State-PA' .
 
Now we will update data_file_override, Navigate to data_file_overide column and click on Premium Editor and Paste below mentioned Json:

[{   "currentDataFileName": "HICC - 1 Zip code or state in 3 States",   "currentDataFileStatus": "WIP",   "replacementDataFileName": "HICC - 2 Zip codes in PA",   "replacementDataFileStatus": "WIP"}]

Click on save.

         18 Now click on 'Save & Exit' the Data File.


  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 3
  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:
  • To maintain a clear Learning history, we have followed the best practice of cloning all the entities before getting into the core action steps.
  



Feedback and Knowledge Base

(thinking…)