3.22.4.3 Test execution with reporting to external repositories

If your Project is joined to an external repository 3.22.4.1, and you have added task IDs to one or more items in your Project 3.22.4.2, then you will be able to report the test results to the repository after the test has run. The test run can be either via the ITE or via the command line testexec.

\includegraphics[height=2cm]{lightbulb} 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.22.4.3. To report to ALM systems after running a test via testexec, you must also manually trigger the recording 3.22.4.3.

When reporting is triggered, the following happens:

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 Status column, you will see whether there are any reports pending. You can see various statuses in this column:

    Not configured:
    if you have not configured ALM reporting for the Project , or if the relevance of the test run was set to false when the test was started.
    Not yet reported:
    if reporting was configured for the Project , and there is information available to be reported that has not yet been reported, e.g. from a test run via testexec. You will also see this status if you have run a test via the ITE that could not report to the ALM system due to e.g. a connection problem. This allows you to report test results later, once the problem has been resolved.
    Reported:
    this status will be shown if you have run a test with reporting configured via the ITE , which reports automatically. It will also be shown if you have chosen to report to the ALM system after running a test via testexec. This status will also be shown even if the test run was not linked to any tasks, but reporting is configured for the Project . It can be understood as any reporting that was necessary has been carried out.
    Report discarded:
    if reporting information was available, but the information was discarded and therefore not reported. You can do this by selecting the option to discard a pending report from the context menu. This status will also be shown for any test runs in a Project that you import that had the status Not yet reported when the Project was exported.
    Marked as non-relevant:
    you will see this status for any test runs that were marked as relevant when the test was started and which have information to report (status: Not yet reported),but which you then mark as non-relevant by toggling the relevance in the Test Result Summary View . This status means that you could report or discard the information, but only if you re-toggle the test run to be relevant.
  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 Status column changes from Not yet reported to Reported. If an error occurs, then the status remains as Not yet reported.
  5. If you do not want to report the test results to an ALM tool, you can discard the reporting information by selecting the option to discard a pending report from the context menu. This changes the status in the ALM Report Status column from Not yet reported to Report discarded.



Copyright BREDEX GmbH 2014. Made available under the Eclipse Public License v1.0.