Page History
...
| Test Type | Number of Tests |
|---|---|
| Manual | Number of tests that are step/script based; usually these are known by "manual" (even though "manual" is a rough simplification) |
| Gherkin | Number of Gherkin based tests; usually these correspond to Cucumber test scenarios, with Test Type "Cucumber", but may also refer to other Gherkin based frameworks |
| OtherUnstructured | Number of tests that are neither scripted nor Gherkin based; usually these correspond to unstructured tests; this includes the tests having Test Type "Generic", "Exploratory". Generic automated test scripts are usually included here; exploratory tests also., etc. |
| Info | ||
|---|---|---|
| ||
If you wish to count Tests by custom Test Types, you can do so. See more information ahead on how to customize this report. |
...
The output will have the following information.
Requirements covered by these Tests
...
- on the "Requirements" section,
- copy "Summary" (i.e., insert a column next to it and copy the values from the existing "Summary" column)
- change the contents to
- ${Links[j].Severity}
Exercise: show a Test step custom field on the Test details
Let's say we have a "StepField1" test step custom filed configured for our project and that it might be used in some test steps
...
of some Tests.
- Go to the Test Details section
...
- Add the "Step Custom Fields" column to the table
- Add the name of the test step custom field along with the value
...
- in the
...
- content cell
- StepField1: ${wiki:TestSteps[
...
- n].StepField1}
Keep in mind that you cannot easily iterate through all such custom fields with 1 statement, you need to target each one individually by name.
Performance
Performance can be impacted by the information that is rendered and by how that information is collected/processed.
...
| Info | ||
|---|---|---|
| ||
|
Known limitations
- for In the base version of the template, modular tests , support only two levels are shown up to 2 levels of hierarchy (i.e. the test steps from the main Test and the steps of any Test called from the main Test)base test calling test A then test A calling test B). You will see detailed regular steps for level 1, but only the note about using callTest for level 2.
- You can expand the number of levels by repeating the loop.
- datasets for data-driven tests are not shown/processed