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.
When developing test cases in Qualitia, you While adding or editing a test case, You can provide data that a test case can use in the following two ways:
...
Click the Test Data button present in the right pane.The Test Data Explorer opens.
Click
(Edit Data button) to start adding or editing values in the Test Data Explorer. The whole test case is locked for that user.The following values are displayed in the second row.
TC Iteration: Enter the number for every TC Iteration. There must be at least one TC Iteration for executing the test case.
Selection: Enter True or False for enabling or disabling iterations. Disabled iterations (False) are not considered when the test case is executed.
DataSetTag: Enter a label for identifying the dataset in the test case execution report. Entering data in this column is optional.
...
| Info |
|---|
|
...
DataSetTagQualitia 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 ReportThe 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.
|
