Ansicht
Dokumentation

RBAMTEST_AUNIT_RESTRICTIONS - RBAM Restrictions API Unit Test (debugging HOWTO in documentation)

RBAMTEST_AUNIT_RESTRICTIONS - RBAM Restrictions API Unit Test (debugging HOWTO in documentation)

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
Diese Dokumentation steht unter dem Copyright der SAP AG.
SAP E-Book

Verwendung

The report RBAMTEST_AUNIT_RESTRICTIONS is a launcher for the ABAP unit tests related to the RBAM Restrictions API. This document describes how to debug individual test cases.

Integration

The ABAP unit tests for the RBAM Restrictions API have one generic test method TEST_ALL, which performs invocations of the RBAM Restrictions API based on XML files stored in the MIME repository. These XML files contain input for an invocation of the RBAM Restrictions API, and the expected output.

Voraussetzungen

If you need to debug any of the XML-based test cases performed by the generic test method TEST_ALL, you'll first need to activate the checkpoint group RBAM_RUNTIME_UNIT_TEST via transaction SAAB. Enter the checkpoint group name into the text field, and press the "Activate" button. This will activate the checkpoint group for your user.

Funktionsumfang

If you just want to run the RBAM Restrictions API ABAP Unit tests without debugging, leave the input field "Breakpoint on XML file" empty, and execute (F8). If any of the test cases fail during execution, you will get a standard ABAP Unit visualization of the results.

For all non-generic test methods, you'll be able to see the failing test method name with a red traffic light. Debugging these test cases can be done using the standard navigation features of the ABAP Unit result visualization.

For the generic test method TEST_ALL, you'll see the name of the XML file whose test case failed right at the start of each error message emitted by the test. For instance, if the test case contained in XML file TEST_U31_RETR.XML fails, each error message for this test case will start with exactly this file name.

Selektion

To debug one of the XML files processed in the generic test case TEST_ALL, you can enter the name of this XML file into the input field "Breakpoint on XML file". You can either get the name of the XML file from the ABAP Unit result visualization as described above, or by looking at the list of files in MIME repository folder

/SAP/BC/RBAM/Testdata/RBAM Restrictions API Unit Test/

To browse the MIME repository, you can for example use the MIME repository browser integrated into the ABAP workbench (SE80 -> MIME Repository).

The file names must be entered without any path prefix. Case is being ignored.

Standardvarianten

n/a

Ausgabe

If all tests pass successfully, the report will only output a corresponding status message. If any tests fail, the standard ABAP Unit result visualization will be presented.

Aktivitäten

n/a

Beispiel

One example of a valid input for the field "Breakpoint on XML file" is:

test_u31_retr.xml






Vendor Master (General Section)   BAL Application Log Documentation  
Diese Dokumentation steht unter dem Copyright der SAP AG.

Length: 2973 Date: 20240520 Time: 073410     sap01-206 ( 64 ms )