Clean ABAP The Golden Rules

CLASS a DEFINITION INHERITING FROM

Names Methods: Object orientation
Don’t mix stateful and stateless in the
Use descriptive names Prefer instance to static methods
max_wait_time_in_seconds, iso3166tab.
same class METHODS a
CLASS-METHODS a
Language Classes: Scope
Public instance methods should be part
Members PRIVATE by default,
Prefer object orientation over of an interface
PROTECTED only if needed
imperative programming INTERFACES the_interface.
I.e. classes over functions and reports Testing: Principles METHODS a

Prefer functional over procedural Write testable code Methods: Method body
language constructs There are no tricks to writing tests, there are only Do one thing, do it well, do it only
E.g. index += 1 or index = index + 1 tricks to writing testable code. (Google)
Instead of ADD 1 to index Descend one level of abstraction
Enable others to mock you do_something_high_level ( ).
CLASS my_super_object DEFINITION. DATA(low_level_op) = |a { b }|.
Comments INTERFACES you_can_mock_this.
Express yourself in code, not in Keep methods small
Readability rules 3-5 statements, one page, 1000 lines
comments given_some_data( ).
do_the_good_thing( ).
Delete code instead of commenting it and_assert_that_it_worked( ). Methods: Parameter number
Aim for few IMPORTING parameters, at
Formatting Test classes best less than three
Be consistent Call local test classes by their purpose METHODS a IMPORTING b c d e
CLASS unit_tests
Optimize for reading, not for writing CLASS tests_for_the_class_under_test Split methods instead of adding
Constants OPTIONAL parameters
Code under test METHODS a IMPORTING b
Use constants instead of magic Test interfaces, not classes METHODS c IMPORTING d
METHODS x
numbers DATA cut TYPE REF TO some_interface IMPORTING b
E.g. typekind_date instead of 'D' DATA cut TYPE REF TO some_class D

Tables Injection RETURN, EXPORT, or CHANGE exactly

Use the right table type
HASHED: large, filled at once, never modified,
read often
SORTED: large, always sorted, filled over time or
modified, read often
STANDARD: small, array-like
Booleans
Use XSDBOOL to set Boolean variables
empty = xsdbool( itab IS INITIAL )
Conditions
Try to make conditions positive
IF has_entries = abap_true.
Consider decomposing complex
conditions
DATA(example_provided) = xsdbool(…)
IF example_provided = abap_true AND
one_example_fits = abap_true.
Ifs
Keep the nesting depth low
ELSE.
IF <other>.
ELSE.
IF <something>.
Regular expressions
Consider assembling complex regular
expressions
CONSTANTS classes …
CONSTANTS interfaces …
… = |{ classes }|{ interfaces }|.
Classes: Object orientation
Prefer objects to static classes
Prefer composition over inheritance
DATA delegate TYPE REF TO
Use test seams as temporary one parameter
METHODS do_it
workaround EXPORTING a
They are not a permanent solution! CHANGING b
Don’t misuse LOCAL FRIENDS to invade Error handling: Return codes
the tested code
CLASS unit_tests LOCAL FRIENDS cut.
Prefer exceptions to return codes
METHODS check RAISING EXCEPTION
cut->db_reader = stub_db_reader
METHODS check RETURNING result
Test Methods Don’t let failures slip through
DATA(result) = check( input )
Test methods names: reflect what’s IF result = abap_false.
given and expected
METHODS accepts_emtpy_user_input Error handling: Exceptions
METHODS test_1
Exceptions are for errors, not for
Use given-when-then
given_some_data( ).
regular cases
do_the_good_thing( ). Use class-based exceptions
assert_that_it_worked( ).
METHODS do_it RAISING EXCEPTION
“When” is exactly one call METHODS do_it EXCEPTIONS
given_some_data( ).
do_the_good_thing( ). Error handling: Throwing
and_another_good_thing( ).
Throw one type of exception
assert_that_it_worked( ).
METHODS a RAISING EXCEPTION b c d
Assertions Throw CX_STATIC_CHECK for
Few, focused assertions manageable situations
assert_not_initial( itab ). RAISE EXCEPTION no_customizing
assert_equals( act = itab exp = exp ).
Throw CX_NO_CHECK for usually
Use the right assert type unrecoverable situations
assert_equals( act = itab exp = exp ).
RAISE EXCEPTION db_unavailable
assert_true( itab = exp ).
Assert content, not quantity Error handling: Catching
assert_contains_message( key )
assert_equals( act = lines( messages )
Wrap foreign exceptions instead of
exp = 3 ). letting them invade your code
CATCH foreign INTO DATA(error).
Assert quality, not content RAISE EXCEPTION NEW my( error ).
assert_all_lines_shorter_than( … ) RAISE EXCEPTION error.

Clean ABAP The Golden Rules v1.1.1 PUBLIC https://github.com/SAP/styleguides/blob/master

/clean-abap/cheat-sheet/CheatSheet.md