You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RISK LEVEL describes the effects that a test can have on the data security of the system:
30
30
31
-
• CRITICAL - such as changes to system settings or Customizing
32
-
• DANGEROUS - such as changes to persistent data
33
-
• HARMLESS - no effects on persistent data or system settings
31
+
• CRITICAL - such as changes to system settings or Customizing;
32
+
• DANGEROUS - such as changes to persistent data;
33
+
• HARMLESS - no effects on persistent data or system settings.
34
34
35
35
The RISK LEVEL is assigned by the following extension to the CLASS DEFINITION statement of a test class:
36
36
37
-
• RISK LEVEL CRITICAL - default
38
-
• RISK LEVEL DANGEROUS
39
-
• RISK LEVEL HARMLESS
40
-
37
+
• RISK LEVEL CRITICAL - default;
38
+
• RISK LEVEL DANGEROUS;
39
+
• RISK LEVEL HARMLESS.
41
40
42
41
### Duration
43
42
Definition
44
43
The DURATION property allows you to define an expected runtime for all methods of a test class.
45
44
46
-
• SHORT - within the blink of an eye ( < 10 seconds )
47
-
• MEDIUM - take a sip of tea ( < 2 minutes )
48
-
• LONG - get another cup
49
-
50
45
At runtime the cumulated duration of all test methods is measured. If the actual duration exceeds the expectation ABAP Unit will raise an alert.
51
46
Please not the cumulated duration contains also system activities as program compilation. In case of doubts it is recommend to choose the higher category.
52
47
53
48
Maintenance
54
49
Use on of the following key words in the CLASS DEFINITON statement of a test class to specify the duration category:
55
-
• DURATION SHORT (default)
56
-
• DURATION MEDIUM
57
-
• DURATION LONG
50
+
51
+
• DURATION SHORT (default) -within the blink of an eye ( < 10 seconds );
52
+
• DURATION MEDIUM - take a sip of tea ( < 2 minutes );
53
+
• DURATION LONG - get another cup.
54
+
58
55
Purpose
59
56
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
57
With help of this classification of the duration the test runner is able to detect these situations and cancel the execution.
0 commit comments