Hierarchy
⤷ BC-DWB-TOO-UT (Application Component) ABAP Unit
⤷ SABP_UNIT_TYPES (Package) INTERNAL: NO REUSE - DDIC type definitions
Basic Data
Data Element | SAUNIT_D_TASK_RUN_MODE_USER |
Short Description | Execution mode of test tasks |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SAUNIT_TASK_RUN_MODE_USER | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Mode |
Medium | 15 | Mode |
Long | 20 | Mode |
Heading | 0 |
Documentation
Definition
The execution mode of a test task defines that the tests are executed within one of the following ABAP runtime session types:
- In a separate external session
- In a separate internal session
- In a separate internal session with runtime protection
In separate external session
ABAP Unit runs the unit tests in a second work process. If runtime monitoring is active, tests that exceed the time limit get terminated with an error. Technically, this is implemented by an invocation via asynchronous RFC.
In a separate internal session
The test runs in its own internal mode (using a submit). If runtime monitoring is active, tests that exceed the time limit cause an error in the runtime log. However, the test execution does not get terminated.
In a separate internal session with runtime protection
In addition to the separate internal session, a runtime abortion will not terminate the test task. Runtime abortions will be added to the ABAP Unit error log instead. The details of the abortion can be reviewed by means of transaction ST22 also.
This technique is limited to the internal session started by the ABAP Unit framework. If test methods implicitly or explicitly make use of a further SUBMIT the runtime protection will be lost.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 710 |