Skip to content

Process to make your Tests 'Data-Driven'

← Data-Driven Testing w/ Worksoft SaaS (without Programming!)
Before you start to think about making your automated tests 'Data-Driven' you are expected to accomplish the following tasks:
  1. Create your Test Scripts (as you would normally do with QaSCRIBE) 
  2. Upload the Test Scripts into Worksoft SaaS
  3. Create your Test Scenario(s) by assembling Test Scripts
  4. Create the Testing Contexts for your Scenario
  5. Validate your Test Scenario(s) for each of the Testing Context(s) of interest to you
  6. Create and Execute (certify) your Run Definitions for all the Testing Context(s) of interest to you
Please note that when you do the executions in step 4 and 5, Worksoft SaaS will use the 'data' (inputs/expected outputs) that is, for lack of better words, hard-coded/hard-wired into the Test Scripts when they are created in QaSCRIBE or edited/updated within Worksoft SaaS.

Once you have 'certified' Run Definitions and/or Test Scenarios, you are ready to make these automated tests into 'Data-Driven'.

To make the tests 'Data-driven' follow these steps:
  1. Create the Data Definitions (that define the structure of your Data Files) in Worksoft SaaS.
  2. Create and Upload the Data Files that have the data sets (test inputs and expected outputs) that you would like the tests to loop through into Worksoft SaaS
  3. 'Parameterize' the Test Scripts (actually relevant "Instructions" within the Scripts) that you want to iterate or loop through data sets from the Data File after 'attaching' the relevant 'Data Definition' to each Test Script
  4. 'Bind' the 'Data File(s)' that you want Worksoft SaaS to dynamically feed the data from when the test is executing within Worksoft SaaS, and
  5. Specify using the 'Data-driven Option(s)', how you want Worksoft SaaS to react when there are contiguous failures across data iterations of a loop. You can either tell Worksoft SaaS to just abort the current Data Loop when there are N consecutive failures and let the other scripts outside the current loop to execute OR tell Worksoft SaaS to abort the entire test. This level of granularity will give you the ability to avoid 'run-away' tests. 
As you can very well see from the process outlined above, making your tests 'Data-driven' is a process that "builds upon" the process that creates and validates your 'non-data-driven' tests. 

While Worksoft SaaS lets you assemble and validate Test Scenarios directly in a Data-Driven mode, it is recommended that you assemble and validate Test Scenarios in a non-data-driven mode first before you proceed with executions in the data-driven mode. We believe that adopting/following such a best practice will go a long way in saving a lot of debug time later.

Please note that even if you make your tests 'data-driven', you can by a single click, make your tests execute as a non-data-driven mode. This and many other options that control 'Data-driven' tests are available for you to use on the 'Bind Summary' tab of your tests (Scenarios and Run Definitions).


Feedback and Knowledge Base

(thinking…)