Lesson 6 Topic 1 Features
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 6 :: Topic 1
1. Data-driven Testing
For a small set of data to be tested, we generally hardcode the values to the Test Scripts and execute the tests.
In this case, it's a good idea to have the data-driven from other sources, apart from the Test Scripts. This is possible with the help of Data-driven Testing.
Data-Driven testing feature in Worksoft SaaS offers powerful and simple-to-use instruments that separate the Test Logic from the Test data. This
helps you structure and maintain the “data” that you want to use to drive “test coverage”.
Data-driven testing can be done using various ways like:
For example, in an eCommerce application, if you are testing 'Discount' offer functionality within the promotions module, you can create a user-defined variable called 'Discount percentage', define the value of the % (let's say 30%) and bind the script logic in your test to that variable.
Data-Driven testing feature in Worksoft SaaS offers powerful and simple-to-use instruments that separate the Test Logic from the Test data. This
helps you structure and maintain the “data” that you want to use to drive “test coverage”.
Data-driven testing can be done using various ways like:
- User-Defined Variables
- Data Files and
- Files
- dbCONNECT
- wsCONNECT
2. User-Defined Variables
User-Defined Variables (UDV's) are name-value pairs that you can define and maintain at the project level and also at a product level within each project.
In Worksoft SaaS, User Defined Variables can be used for many purposes, however, in the data-driven testing, they can be used to decouple the test script logic from the test data.
For example, in an eCommerce application, if you are testing 'Discount' offer functionality within the promotions module, you can create a user-defined variable called 'Discount percentage', define the value of the % (let's say 30%) and bind the script logic in your test to that variable.
If the value of % needs to change (let's say 40%), you can go back to the Discount Percentage UDV, update it and execute the tests.
In order to use the UDV in Data-Driven Testing, we will bind the Test Script values to the respective User Defined Variables for parameterization, so that the test logic comes from the Test Scripts, however, the changing input values come from UDV's.
In order to use the UDV in Data-Driven Testing, we will bind the Test Script values to the respective User Defined Variables for parameterization, so that the test logic comes from the Test Scripts, however, the changing input values come from UDV's.