Qualitia Automation Studio (QAS) enables you to easily manage Test Data, the set of data that is used during execution. You can view test data, add or delete, and edit existing test data. The Test Cases and Tasks can be reiterated multiple times using test data. Let’s see how this works!
📚Prerequisites
User should have the QAS - Client installed.
User should be assigned to an existing project.
A test scenario should exist.
🔑Privileges
User should have the below privileges to:
Import Feature: Import test cases or other project elements.
Manage Custom Action Code: Oversee the custom action scripts in projects.
Manage Objects: Control the objects within the testing environment.
Manage Scenarios: Control the scenarios within test suites.
Synchronize Objects: Keep test objects synchronized.
Test Development: Create and update test cases.
A test case contains two types of test data:
Static Data - As the name suggests, static data denotes a single static value for a parameter of an action. The static data must be enclosed in double-quotes (""). For example, if a step contains an object as username and Action as Set, then under the Parameter column, enter “John”.
Whenever you change the static data for a step of a task, the change is reflected in all the associated test cases.
Parameterized Data - You can define multiple sets of data to execute a test case in multiple iterations using the Test Data explorer. Also, you can have multiple task iterations within a test case iteration.
You can only view the parameters added for the parameterized data under Test Data.
Test Data icon will be enabled only if the test case contains parameterized data, if all the data is static, it will be disable.
To parameterize the test data:
Login to QAS - Client.
Access Develop from left navigation to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios.
Click the Expand option on a test scenario, where you can view all its test cases.
Open the test case in which you want to add test data or edit its existing test data.
In the test case, under the Parameter columns, for the data you want to parameterize, replace the existing values with a unique value without enclosing in double-quotes.
Click Test Data at the bottom left corner of the Test Explorer screen.
Clicking Test Data will open the Test Data explorer.
To add a test case iteration, click + Add TC Iteration. It will insert a blank row below the selected iteration and auto generate the Itr. N.
DataSetTag: Enter a unique value for a data set test case iteration. DataSetTag simplifies finding a test case iteration in the test case execution report.
Toggle: Toggle on the iteration to enable the execution for the test case iteration or toggle off the iteration to disable the execution for the test case iteration. You must enable at least one test case iteration to execute the test case.
Enter the values in their relevant formats for each parameterized data.
Enter $NULL$ in the cell where you want to have a blank value by clicking on Add $NULL$ in blank from the More Options.
You can move and resize the Test Data explorer.
You can import test data for a test case from an excel file and also export it as an excel file.
The Total TC Iteration shows the total number of iterations in test data.
If the test case contains tasks, the first row displays the task names. Each task covers its associated parameterized data in the second row.
Click + Add task Iteration to add a task iteration within a test case iteration.
Clicking + Add task Iteration will insert a blank row after the test case iteration.
Enter the values in their associated format for the task parameters.
The values added for parameters of a task are not duplicated in the same tasks that are present in other test cases.
You do not need to enter the values for the parameters that are not associated with task iterations as they are not considered in the task iteration executions.
After adding or editing all the required data, click the Save button on the Test Case Editor screen.
Click the Test Data button present in the test case editor screen to close the Test Data explorer.
You can now Dry run the test case to verify whether the test data meets the test requirements.
Test Data explorer parameterizes the values that are present under the parameter columns of the test case and task steps only.
If you do not define add test data for a step, then that step and its parent task is underlined with red color. Also, the test case and test scenario are underlined with red color in the left pane of Test Case screen.
Additional actions you can perform with Test Data:
Toggle - Toggle on or off the TC iteration. Using master toggle, we can mark or unmark all the iterations.
Error Navigator - If there are any errors in our data, we can navigate to that particular error using error navigator.
Delete - Delete the task iteration or the TC iteration.
More Options - Add $NULL$ to all the blank rows by clicking on more options.
Find - Search the values using find.
Expand All - Expand all the iterations.
Collapse All - Collapse all the iterations.
Hide ‘Skipped or unmarked’ Data - This will hide/unhide the skipped columns under the Test Case editor.
Import - A test case or task can be imported using an Excel file.
Export - Export test data in an Excel.
Maximize
Undo
Redo
Refresh
Popout
💡Golden Nuggets: Best Practices for Test Data Management
Adding multiple iterations: We are restricted to add one iteration at a time, and this can be time consuming. In order to save time and add multiple iterations at a time, QAS allows you to export data to the local and reuse it by just a drag and drop method to add multiple iterations. You can add multiple iterations using the Excel and import it again.
Getting errors in Test Data: You might get errors during execution and would not understand Why? This might be due to the blank cells in the test data. To avoid it, enter $NULL$ in the cell where you want to have a blank value by clicking on Add $NULL$ in blank from the More Options. This will add $NULL$ to all the blank cells and you can avoid the errors.
🔧 Got a problem? Let’s fix!
Unable to edit iteration cell: When you add a task iteration for any of the test cases, you will be allowed to edit or parameterize the cell only under that task. However, when you will add this iteration, an entire row will be added and there will be cells for the test case as well as the other tasks under the same test case. These cells however will be inactive, and you won't be able to edit them.
For example: You have added a task iteration for Task1, which is part of Test Case1. Test Case1 consists of one more task that’s Task2. Now, when you add an iteration, a row will be added with cells under Test Case1, Task1, as well as Task2. However, only the cell under Task1 will be active and you will be able to add value to it, others will be inactive.
Not able to copy task iteration from one task to another: You will be able to copy task iteration from one task to another, only if the schema of two tasks is same. They should have same number of parameters.
For Example: If Task1 consists of one parameter key* and Task2 consists of two parameters key* & InputString*, you won't be able to copy a task iteration from Task1 to Task2 or vice versa. However, if Task1 contains Key* and Task2 Inputstring*, the task iteration can be copied.
📞📚 Here to Help: Support and Resources
If you have questions that are not addressed in the documentation, you may raise them in the Qualitia Community.