Page History
...
The following screenshots show the Jenkins configuration.
We could eventually fill/identify the Test Environment to associate to the Test Execution based on the Postman's Environment being used if it would make sense for us to analyze the results on a per-environment basis.
A Test Execution will be created containing results for all tests executed.
Unstructured An unstructured (i.e. "Generic") Test issue issues will be auto-provisioned the first time you import the results, based on the identification of the test (see notes for possible Newman reporters above). If you maintain the test case name and the respective test suites, the Test The "Generic Definition" field on the Test issue is used as a way to uniquely identify the test.
| Info | ||
|---|---|---|
| ||
Tests will be reused on subsequent result imports |
...
as long as you don't change what contributes to the calculation of the test's unique identifier (i.e. "Generic Definition" field); otherwise, new Tests will be auto-provisioned. Therefore, and depending on the Newman reporter being used, if you change the Postman test description or the folder containing the test, it will lead to new Tests in Jira as Xray will consider them to be new. |
...
Tags can also be used to cover an existing requirement/user story (e.g. “ROB-11”): when a requirement issue key is given, a link between the test and the requirement is created during the results import process.
Otherwise, tags are mapped as labels on the corresponding Test issue.
...
Within the execution screen details, accessible from each row, you can look at the Test Run details which include the duration, overall result, and also specifics about each keyword, including duration and status.any eventual error message.
