From the Test Result Summary View (Section 3.22.3, “Working with the Test Result Summary View”), you can generate reports of your test runs over time using the BIRT reporting engine.
![]() |
Only test runs that have been marked as relevant are included in the generated BIRT reports. You can change the relevance from the Test Result Summary View (Section 3.22.3.4, “Changing the relevance of a test run”). |
The ITE offers a selection of example reports:
This report shows a table of all failed tests for the time chosen, whose relevance is set to true and whose name does not include BROKEN. The comment title that can be entered in the Test Result Summary View (Section 3.22.3.9, “Entering comments for test runs in the Test Result Summary View”) is also shown. This report is useful for delivering daily status reports of the tests.
This report shows a list of executed, relevant Test Suites over the time period selected. For each day in the time period, there is a colored block for the Test Suite to display its status. Green means that the test ran without any errors. Red means that the test ran, but with errors. Yellow means that the test ran more than once on that day. White means that the Test Suite did not run on this day. This report is useful for teams with large amounts of Test Suites who need to ensure on a daily basis that all Test Suites were started. Test Suites that were not run at all during the selected time period are not displayed.
This report shows the duration of the chosen tests.
This report shows the proportion of executed, failed and non-executed Test Steps for a test. This report is most useful when one specific Test Suite is compared to see its progress over time.
This report shows a graph of the percentage completion for the selected Test Suites for the dates given. There is also a list of the AUTs, Test Suites and test runs.
This report shows the same details as the Test History report, but instead of showing the test results in percentages, shows the actual amount of Test Steps executed. It also shows the difference between expected and executed Test Steps.
This report shows the same details as the Test History Absolute report with any code coverage information that is available for the chosen test runs.
This report gives out the full test details up to the given nesting level.
This report shows a table of the Test Result Summary View for the dates and tests chosen.
To start a report, click the arrow next to the
”Create Report” button
and select the report you want to generate.
![]() |
If you are not already connected to the database, then a dialog will appear to create the connection (Section 3.4.1, “Logging in to the database”). |
The BIRT report viewer starts (the first time it starts it may take some time).
The parameters for the report are displayed:
In this section, specify which time frame the report
should be generated for (either from a specific date,
or using the options yesterday, now, last
week etc.) as well as for which Project,
Test Suite, Test Job and the operating system. The
details in the selection section are combined using
and. SQL syntax can be used (e.g.
%
is used as a wildcard for any
number of any characters, _
is used
as a wildcard for one character).
Some reports are generated for a specific test run. The test run ID of the currently selected test summary is entered by default, but you can enter a different run.
For the Testresult and TestresultError reports, you must also specify the nesting level (how many levels in the hierarchy should be shown) and the ID of the test run you want to generate the report for. The test run ID for each run can be seen in the Test Result Summary View.
Click ”OK” to start the report generation.
Once the report is ready, it will be shown in the BIRT viewer.
Hover over the points on the graph in a report to see any additional information about the point (comment, data value etc.).
You can click through the report’s pages in the viewer and also export the report as a PDF.
![]() |
The option Auto when exporting a report leads to the right-hand side of the report being cut off. |
![]() |
You can also create your own reports to execute (Section 3.23.2, “Writing your own BIRT reports”). |