Test Case page

Test Case Details page includes several tabs with various data related to the test suite:

  1. Test Case Information tab shows general information about the test case, linked test objects and test suites. This tab looks:

    tc info

    On this tab you can:

    1. Edit the test case title, message or partner (to start editing click on edit button). To save changes click on save button, to reset - reset.

    2. View Agent Object clicking on Agent Object Title. It opens Integration Object Details page.

    3. View Test Objects clicking on required Test Object Title. It opens Integration Object Details page.

    4. View Test Suites that the test case is linked to clicking on required Test Suite Title. It opens Test Suite page.

    5. Add or remove Test Object(s) clicking on plus or decline buttons respectively.

      Test Objects are only from the same platform as Agent Object can be added.

    6. Add the test case to new or existing Test Suite or remove the test case from Test Suite(s) clicking on plus or decline buttons respectively.

  2. Messages tab shows inbound/outbound messages in the test case and looks differently for PRO and CPI Agent Objects:

    1. For PRO Agent Objects:

      tc messages pro

      The following actions can be executed for both PRO and CPI Agent Objects:

      1. Calculate ordering numbers calculates ordering numbers based on configuration on Recording Configuration tab of related integration object or suitable Shared Configuration.

      2. Calculate file type and encoding calculates messages file types and encoding based on Encoding Determination configuration if encoding determination rules exist or standard algorithm if they don’t exist.

      3. Options available in the message’s menu button:

        1. View/Edit message opens 'Message Details' page.

        2. Delete message group removes all messages with the same 'Inb. Group' as the one that the option selected for. It’s possible to delete only message or delete messages and related test run results (reports will be rebuilt in this case).

        3. Copy message group copies all messages (with the same 'Inb. Group' as the one that the option selected for) to selected test case(s).

        4. Change interface metadata opens 'Change message interface metadata' dialog box:

          change message metadata

          You can configure required changes here. Change messages globally applies changes to all messages with 'Source Message Interface Metadata'.

        5. Download downloads message xml file for PRO and file without extension for CPI.

    2. For CPI Agent Objects:

      tc messages cpi

      The following actions can be executed for CPI Agent Objects:

      1. Generate groovy scripts test data generates groovy scripts (see Groovy scripts unit testing).

      2. Options available in the message’s menu button:

        1. Build groovy script generates groovy script (see Groovy scripts unit testing).

        2. Generate test data for current message generates json.

  3. Messages Anonymization tab helps to configure anonymized test case based on current test case and looks:

    tc message anonym
    It works only for XML messages.

    On this tab you can:

    1. Add message mappings selecting Message group id and clicking twice on the element you want to anonymize:

      message anonymization create
      You also can add message mappings clicking on plus button in Applied mappings table. In such case you have to define Element path by yourself.

      It opens 'Create mapping' dialog box:

      create mapping

      Select desired function:

      • Multiply by random value from range multiplies source values by a random number from the range defined by values of From and to properties. If you want to get integers, set Count of number after a decimal point property value as 0, otherwise, define desired value. Example with filled properties:

        create mapping random ex

        To test function enter Test value and click on Test function.

      • Generate value from template generates values from Template property value. You can define template using special characters ('#' for number, '?' for uppercased character, '*' for lowcased character, e.g. ### - template for 3 random numbers) or anonymization variables defined in Anonymization variables, e.g. ${firstname} ${lastname}. Example with filled properties:

        create mapping template ex

        To test function click on Test function.

    2. Edit message mapping clicking on edit button in Applied mappings table.

    3. Delete message mapping clicking on decline button in Applied mappings table.

    4. Create new test case with anonymized data clicking on Clone anonymized test case button. It opens 'Clone anonymized test case' dialog box:

      clone anonymized tc

      After submitting the dialog new test case will be created.

  4. Testing Results tab shows the test case run results and looks:

    tc results

    On this tab you can:

    1. View Test Object clicking on 'Test Object'. It opens Integration Object Details page.

    2. Run the test case clicking on run or run on buttons:

      • Run uses static links to test objects defined in the test case.

      • Run on resolves these links dynamically at the moment of test run. It is possible to see how these links are resolved through Current Mapping Configuration button - it opens 'Mapping Configuration' dialog box:

        mapping configuration

        There are Agent Objects (parent nodes) and Test Objects (child nodes) in opened dialog box.

Test cases aren’t run on deleted test objects. Such objects are skipped and listed in a warning message box (Test cases will not be run on the following test objects because these objects are deleted: …​), while the other test objects and test cases of the run are processed. A test suite in which no test case has a runnable test object isn’t run at all, and no test suite run is created.

  1. Select test case run result(s) and:

    1. Poll remote messages and Open Last Polling Result.

      Since Figaf Tool 2.15 automatic polling is added for SAP CPI Agents. Once the messages have been run successfully, automatic polling is started.

      Since Figaf Tool 2.15.2 active polling statistics can be viewed. If there is polling in progress for the integration objects and you open another poll remote data dialog, then

      • recordings/test runs which are in both polling requests will be marked as SKIPPED_AS_DUPLICATE and statistics will be copied from original item and shown on UI in the new one.

      • recordings/test runs which are not in the original polling request will be SKIPPED in the new one.

      Since Figaf Tool 2305 polling will not be started if there is already a started polling requests with same objects in progress or polling has been already completed for all selected objects.

      If you have polled almost all messages and you just need to poll small number of messages to finish testing, you can enable option Ignore messages cache during polling on Application configuration page. When this option is enabled, already polled messages won’t be skipped. It affects performance when the amount of messages is large and you just need to poll small number to finish testing.

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

    2. 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".

    3. Delete the result(s) clicking on red trash.

  2. The options available in result’s menu 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. View results opens Test Run Details page.

    3. Mark as Test Case creates new test case from chosen groups of testing results. Testing results become expected messages in the new test case.

    4. Update Test Case using Test Run Results. It replaces corresponding messages in the current test case by 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 messages of testing result will be copied.

      2. Replace only messages from the test run - only corresponding messages in the current test case will be replaced by messages of testing result. So if the test case has some messages which aren’t used during comparison, these messages will not be deleted.