Skip to content

Commit 438ab81

Browse files
Update db-access-in-ut.md
1 parent 3f482dc commit 438ab81

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

docs/checks/db-access-in-ut.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,7 @@ The pseudo comment must be placed right after the DB access statement.
2525
SELECT XXXXX. "#EC DB_ACCESS_UT
2626
```
2727
### Risk Level
28-
Definition
29-
The RISK LEVEL describes the effects that a test can have on the data security of the system:
28+
Definition: The RISK LEVEL describes the effects that a test can have on the data security of the system:
3029

3130
• CRITICAL - such as changes to system settings or Customizing;
3231

@@ -45,22 +44,18 @@ The RISK LEVEL is assigned by the following extension to the CLASS DEFINITION st
4544

4645

4746
### Duration
48-
49-
#Definition
50-
The DURATION property allows you to define an expected runtime for all methods of a test class.
47+
Definition: The DURATION property allows you to define an expected runtime for all methods of a test class.
5148

5249
At runtime the cumulated duration of all test methods is measured. If the actual duration exceeds the expectation ABAP Unit will raise an alert.
5350
Please not the cumulated duration contains also system activities as program compilation. In case of doubts it is recommend to choose the higher category.
5451

55-
##Maintenance
56-
Use on of the following key words in the CLASS DEFINITON statement of a test class to specify the duration category:
52+
Maintenance: Use on of the following key words in the CLASS DEFINITON statement of a test class to specify the duration category:
5753

5854
• DURATION SHORT (default) - within the blink of an eye ( < 10 seconds );
5955

6056
• DURATION MEDIUM - take a sip of tea ( < 2 minutes );
6157

6258
• DURATION LONG - get another cup.
6359

64-
Purpose
65-
Unit tests consist of source code and can contain errors. It is easy to recognize syntax errors and runtime errors, but endless loops are more difficult to detect.
60+
Purpose: Unit tests consist of source code and can contain errors. It is easy to recognize syntax errors and runtime errors, but endless loops are more difficult to detect.
6661
With help of this classification of the duration the test runner is able to detect these situations and cancel the execution.

0 commit comments

Comments
 (0)