3.27.4.3 Test execution with reporting to external repositories

If you run a test via the ITE which should report to ALM systems, the reporting is triggered automatically once the test has run. If the reporting for the test run encounters an error, then you will be able to manually trigger the reporting later 3.27.4.3. To report to ALM systems after running a test via testexec, you must also manually trigger the recording 3.27.4.3.

When reporting is triggered, the following happens:

• A connection is made to ALM system configured in the Project properties.
• The test results are then analyzed to see if any comments need to be added in the external repository (commenting can be (de)activated for failed nodes or successful nodes in the Project properties, for example).
• If there are comments to be added, the ITE writes one comment per task, as defined in the Project properties. If multiple items in one test run reference the same task ID, or if an item with a task ID is executed multiple times in the same test run, then each test status and result link is written, but all in one comment.

  Tests that have a status other than passed (e.g. failed, stopped, still testing) are considered as failed.

• You can see the status of the ALM reporting in the console view.
• Once a comment has been written, you can see the comment in the external repository. From there, you can click on the link provided to open the test result report in the Dashboard that you specified for your Project . The Dashboard must be already running for this action to succeed. The test results must also still be present in the Database 3.20.3.1.
• The test result report is opened at the node which referenced the current task ID.

  The integration for writing to external repositories can be used with Bugzilla 3.6+, JIRA 5.0+ and HP ALM 11+. Other repositories for which there are Mylyn connectors may also work, but these have not been tested.

Reporting to ALM repositories after a test started via testexec For tests started via testexec, the reporting does not happen automatically. Instead, you must choose to report to ALM from the Test Result Summary View .

1. In a Project that is configured to report to an ALM repository, when a test has run via testexec, you can open the Reporting Perspective and locate the test run in the Test Result Summary View .
2. In the ALM Report Pending column, you will see whether there are any reports pending. This is based on various factors:
   1. ALM Reporting must have been configured for the Project . If no ALM is configured for the Project , then the status in the ALM Report Pending column will be false.
   2. The test run must have been designated as relevant. Non-relevant tests show the status false in the ALM Report Pending column.
3. Select any test runs whose results you want to report to ALM, and click on the "Report to ALM" button on the toolbar. You can also select this option from the context-sensitive menu. If you select multiple test runs, the reporting will take place sequentially for each test run.
4. When you select this option, the reporting will be triggered as described above. If the reporting is successful, the status in the ALM Report Pending column changes from true to false. If an error occurs, then the status remains as true.

   If you do not want to report the test results to an ALM tool, you can switch the status of the ALM Report Pending column from true to false by selecting the option to cancel pending reports from the context menu. Toggling the relevance of the test run to false will also set the ALM Report Pending status to false, but this will also mean that the test results are not exported and not considered for BIRT reports 3.22.8.