Importing Reports

The results of automated test runs can be imported into the system at one of the stages of preparing and releasing a build.

This is usually handled by build servers (or builders) such as Jenkins or TeamCity. The command for importing a test report is given in the hint in the "Test Reports" module. To check whether your report can be imported, use the "Import report" action.

Report formats of automated testing tools available for import:

  • JUnit — a file with testing results in xml format
  • NUnit — a file with testing results in xml format
  • TestNG — a file with testing results in xml format
  • Allure — a zip archive of the directory with testing results

Besides the call stack and other debugging information, it is useful to insert application screenshots into the testing report. Such screenshots form the context for analyzing and reproducing defects. A screenshot is included in the report by the tool you use to run automated tests. For example, in the case of Selenium, this is a small piece of code.

Develop functional and integration automated tests based on the test documentation. Then, after the corresponding test class or test method has been implemented, add a Description annotation in which you specify the identifier of the automated scenario. In this way, in the testing results you can view both the scenario text and the result of testing it.

@Test(description="S-1685")
public void myTestMethod() {
// ...
}

This links the automated test to the original scenario. Problems are much easier to analyze this way, because the original scenario text is visible in the report.

Search results