Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update names of test tools to be exploited #300

Merged
merged 1 commit into from
Mar 20, 2023
Merged

Update names of test tools to be exploited #300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions clean-abap/CleanABAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4595,13 +4595,10 @@ with standard ABAP unit tests and test doubles.
However, there are tools that will allow you
to tackle trickier cases in elegant ways:

- Use the `CL_OSQL_REPLACE` service
to test complex OpenSQL statements
by redirecting them to a test data bin
that can be filled with test data
without interfering with the rest of the system.
- Use the OSQL test environment (`CL_OSQL_TEST_ENVIRONMENT`) to test complex OpenSQL statements
by redirecting them to test data defined in the unit test without interfering with the rest of the system.

- Use the CDS test framework to test your CDS views.
- Use the CDS test environment (`CL_CDS_TEST_ENVIRONMENT`) to test your CDS views.

#### Use test seams as temporary workaround

Expand Down