From 37c1413c6e3b2665f9bab7b6edc53b2417934224 Mon Sep 17 00:00:00 2001
From: ConjuringCoffee <72548231+ConjuringCoffee@users.noreply.github.com>
Date: Mon, 20 Mar 2023 15:42:55 +0100
Subject: [PATCH] Update names of test tools (#300)

---
 clean-abap/CleanABAP.md | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/clean-abap/CleanABAP.md b/clean-abap/CleanABAP.md
index 186803fa..4ad7b174 100644
--- a/clean-abap/CleanABAP.md
+++ b/clean-abap/CleanABAP.md
@@ -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