Test Run Details page

Test Run Details page looks:

test run details page

On this page you can:

  1. Select data Perspective for the table:

    1. Tree Table is default value for all regression test cases except aggregation ones (for baseline and aggregation test cases Tree Table mode is disabled). This table has a merged functionality of Message runs tab and Results tab. Tree Table represents 2 tables: old Test Run Results table (i.e. Flat Table in the new terms) and Message Runs table on the other tab.

      test run details tree table

      It has full pagination, filtering and sorting. Sorting is a bit tricky because of pagination: if you sort by column belonging to a Message Run, it should work naturally, just like in all other tables. But if you sort by Test Run Result columns, Test Run Results will be sorted in scope of each Message Run.

    2. Flat Table is the old Test Run Results table:

      test run details flat table

  2. Poll remote messages.

    Open Last Polling Result button is available after polling remote data and until page is refreshed.

  3. Rerun test case if it’s run in scope of test suite run.

  4. Compare results clicking on check.

    The option reprocesses comparison and report generation asynchronously. It makes sense to execute the option once you have configured a new "ignore rule".
    If comparison fails for a particular test run result, you can view error details clicking on warning.

  5. Open related test case. It opens Test Case Details page.

  6. Open related test suite run. It opens Test Suite Run page. The link is shown only if you run test suite linked with related test case.

  7. Open Agent and Test Objects.

  8. View ignore lists (Applied items ignore expressions and Applied Message properties ignore expressions). IT shows ignore lists configured on Test Configuration tab of Integration Object page.

  9. Open actual test configuration. It opens Test Configuration tab of Integration Object page.

  10. View used comparison configurations. It opens Comparison Configuration dialog.

  11. Execute actions available in run’s menu full button:

    1. Download report.

      Report type can be one of 2 types:

      1. xlsx report:

        • Contains information about test run/test suite run results.

        • By default only failed results are added to xlsx report. If you want to change this behavior, go to Configuration → Application page and enable Show successful messages in the test suite’s report property.

      2. zip archive with 3 csv reports:

        • test-run-metadata.csv - contains common information about test run/test suite run (e.g. test object, counters for success/error/unexpected/not/compared/unfinished test run/test suite run results).

        • diff-report.csv - contains diff report for test run/test suite run.

        • processed-messages-report.csv - contains processed messages report for test run/test suite run.

      The report type is defined from Use bundled CSV report generation strategy property configured on Application configuration page. If it’s true, the report type is zip, otherwise, it’s xlsx.

    2. Mark selected message group as Test Case. It creates new test case from chosen groups of testing results. Testing results become expected messages in the new test case.

    3. Update Test Case using Test Run Results. It replaces corresponding messages in the current test case by chosen messages of testing result. There are 2 strategies available:

      1. Drop all old messages - all old messages will be deleted from the test case and chosen messages of testing result will be copied.

      2. Replace only selected messages - only corresponding messages in the current test case will be replaced by chosen messages of testing result.

  12. Execute actions available in message’s menu button:

    1. View result. It opens Test Run Result page.

    2. Download inbound message, expected result, actual result.

    3. Build groovy script (see Groovy scripts unit testing).

    4. Diffs opens Differences dialog box. Here you can add items (click twice on the required item) and message properties (click on the required message property) to ignore list.

      Add items and message properties to ignore list once.
      differences add to ignore list

    5. Binary diffs opens Differences dialog box (see above) with binary comparison. Current configurations are used for this comparison type.

    6. Diff2Html diffs opens Diff2Html comparison dialog. Current configurations are used for this comparison type.

    7. Ignore step (CPI) adds current step to ignore list.

    8. Browse related messages (PRO) is runtime viewer for related message monitoring entries. It looks for message monitoring entries on the PI system by the currently persisted PI message id (used in id and refId filters). For not received entries we know only the id of the sent message, then once the message is received it’s overwritten by a related AFD message id.

      test run related messages

      From the Related messages dialog it’s possible to open PI message page on SAP system and browse message log in the separate dialog:

      test run message log

      Use these options to analyze the root cause of the UNFINISHED state of the result to check what’s going on on PI system.

    9. Open message monitor (PRO).

    10. Open message monitor via dispatcher (PRO).

  13. Check messages statuses (whether messages have been sent successfully or some error occurred):

    1. Go to Message runs tab

    2. View data in the table.

      test run details page message runs tab