Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Static Data

  • Parameterized Data

Static Data

As the name suggests, static data has 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 be enclosed in double-quotes ("").

...

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 test cases.

Parameterized Data

Qualitia gives you the provision to use multiple sets of data when executing test cases.

...

Info
  • Enter as $NULL$ in the respective cell when you do not want to add a value for a parameter in a TC or Task Iteration.
  • The Test Data screen is movable and resizes up to the full screen.

  • Export and Import a Test Data in an excel file.
  • After saving a test data, if you want to edit again, click  to unlock the test data again.


Validations in Parameterized Test Data 

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

...

In the Test Data explorer, the missing or wrong values are highlighted in red. In case of uploading through the excel file, you can view these messages in the TestDataErrorlog.txt.



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. 

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. 




...