Page Comparison

Test Data are the values used during the test case development. Qualitia comes with a built-in Test Data explorer for adding and updating test data.

While adding or editing a test case, You can provide data that a test case can use in the following two waysA test case contains the following two types of test data:

• Static Data

• Parameterized Data

Static Data

As the name suggests, static  static data has denotes a single static value used when executing test cases. Static data is given in the parameter section against each action in Qualitia. This data should for a parameter of an action. The static data must be enclosed in double-quotes (""). For example, if a step contains an object is as username and Action is as Set, then under the Parameter column, type as enter “John”.

Whenever you change the static data for a step of a task, the change is reflected for all instances of this task across all the in all the associated test cases.

Parameterized Data

Qualitia gives you the provision to use You can define multiple sets of data when executing test cases.It allows multiple iterations of a single Test case or multiple iterations of a single task 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.

...

The Test Data feature ensures effective time management and maximum test coverage with minimum updates to the test case. In a Test Data, a TC iteration flows from left to right, whereas a Task Iteration within a TC iteration flows from top to bottom.

Qualitia Test Data Explorer can be used to add or update test data. When you click the Test Data button, from the Test Cases Editor screen, Qualitia opens a spreadsheet which allows adding or updating Test Data to use while executing the test case.

To add/ edit Test Data:

1. Click the Test Data button present in the right pane.The Test Data Explorer opens.

2. Click Image Removed (Edit Data button) to start adding or editing values in the Test Data Explorer. The whole test case is locked for that user.

3. The following values are displayed in the second row.

   1. TC Iteration: Enter the number for every TC Iteration. There must be at least one TC Iteration for executing the test case.

   2. Selection: Enter True or False for enabling or disabling iterations. Disabled iterations (False) are not considered when the test case is executed.

   3. DataSetTag: Enter a label for identifying the dataset in the test case execution report. Entering data in this column is optional.

1. From the third row, enter the values in their respective formats. The first row displays the different Tasks highlighted in grey color. Each Task covers its parameters in the second row.

2. If you want to add a TC iteration, insert a row and specifying values for TC Iteration number and Selection, then enter the values for the associated parameters.

3. If you want a Task Iteration, insert a row without specifying the TC Iteration number, and then enter the values for parameters. Add more Tasks iterations by inserting new rows.
4. Once all the data is added or edited, click the Save button located in the Test Editor screen.

Validations in Parameterized Test Data 

Test data validations, while saving test data or importing test data through an excel file, are as follows:

Blank Data

To parameterize the test data for a test case:

1. Open the test case in which you want to add test data or edit its existing test data. For instructions on how to open a test case, refer to Adding or Editing a Test Case Manually.
2. 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. 

3. Click the Test Data button to open the Test Data explorer.

4. Click the Edit Data button.
   The test case and test data are locked for other users.
   

5. To add a test case iteration, under the following columns, enter the following details:

   1. TC Iteration: Enter a number for every test case Iteration. 
      Note: After saving the test data, the values in TC Iteration are automatically numbered from 1, even if you provide any number in TC Iteration.

   2. 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, 

   3. Selection: Enter True to enable the execution for the test case iteration or enter False to disable the execution for the test case iteration. You must enable at least one test case iteration to execute the test case, 

   4. Enter the values in their relevant formats for each parameterized data.

      Info
      Enter $NULL$ in the cell where you want to have a blank value. 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.

      
      

6. If the test case contains tasks, the first row displays the task names. Each task covers its associated parameterized data in the second row.
   To add a task iteration within a test case iteration, do the following in the order listed:
   1. Insert a blank row after the test case iteration.

   2. Skip the TC Iteration number, Selection, and DataSetTag.

   3. Enter the values in their associated format for the task parameters only.

      Info
      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.

      
      

7. After adding or editing all the required data, click the Save button on the Test Case Editor screen.
   

   Info
   After saving a test data, to edit test data, click the Edit button to unlock the test data again.

   
   

8. 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. For more information, refer to Dry Run a Test Case. 

Troubleshooting the Issues in Parameterizing Test Data 

The following table provides information to troubleshoot the issues you may face while parameterizing the test data.

...

...

...

...

...

...

...

Parameters Mismatch

...

...

...

...

...

DataSetTag

Qualitia gives you a provision to tag the test case iterations with keywords based on the test data set you to provide for test case execution. These tags enable you to differentiate test case iterations based on the provided test data. Using this feature, you can easily spot the test case iteration, which is failed or has defects just by looking at the suite execution report. Identifying the area where a tester needs to work becomes easy and handy when you add relevant tags to the test case iterations.

Where to add these tags? 

Qualitia users can add these tags at test case iteration level from the test data screen.  

Providing these tags is optional. 

Image Removed

Suite Execution Report 

The tags which you add to the test case iterations are displayed in the test case execution report next to the iteration number.

When executing such test cases, if any of the iterations fails or has defects, it is easy to identify which set of data has issues from the whole set of iterations that are causing failures or adding defects.  

These tags are displayed against the test case name in the suite execution report. 

Image Removed

color. Correct the sequence of parameters or their names. If you have imported test data using an excel file, you can view the missing and wrong values in the TestDataErrorlog.txt.