Skip to content

Lesson 7 Topic 1 Features

← 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.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 7 :: Topic 1

1. Data Files and Data Definitions
In Worksoft SaaS, "Data File” is a construct (instrument) which is used to maintain different “test data” (combinations of test inputs and expected test outputs in tabular format) to meet your test coverage requirements.

Data Files can be created easily by uploading csv files, which in turn can be created using Microsoft Excel or Google spreadsheets.

The structure of the data for the Data File is defined by another construct called 'Data Definitions'. It becomes very easy to understand 'Data Definitions' and 'Data Files' using a "Table" that contains (multiple rows of) data in a Spreadsheet as an analogy.

For Example: You want to test an e-commerce application and the test data of different Products and Categories are available in an external source like a software or Microsoft Excel, then you can convert them into a csv file and upload it into Worksoft SaaS as a Data File.

To create a Data File:
  1. Prepare Data Definition: It is a pre-requisite to creating your Data Files, hence can be created in multiple ways:
  2. Manually or Bulk import after designing the structure for multiple Data Definitions
  3. Once the Data Definition is ready, you 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.
In order to use the Data File in Data-Driven Testing, we parameterize the Test Script values to the respective Data Definition attributes, so that the test logic comes from the Test Scripts, however, the changing input values come from Data Files. Then, we will bind the Data file to either the Run Definition or Scenario that is being used to execute the test.


2. Data Binding
When executing a Run Definition or a Scenario, Worksoft SaaS provides an option to bind the Data file.

This is done in the Data Binding tab which appears after the related Scripts & Scenarios are assembled.

Once the Data File is created and the Test Scripts are bound to the Data Definition, we will be able to see the Data file in the drop-down list in the Data Binding tab.

After the Data file is selected, we can also confirm the binding by looking at the Bind Summary.


3. Data Looping/Iterations
When this Data file is executed in the Data-driven mode, Worksoft SaaS will automatically run the same test (business logic embedded in the test) for each data set (from each row) of the Data File and this is the concept of "Data Looping" (or data iterations).
     
For example, if there are 20 rows of data (20 datasets) in the Data File, Worksoft SaaS executes the test 20 times in an iterative manner by separating the Test logic and using different test data each time.


Feedback and Knowledge Base

(thinking…)