Update CleanABAP.md

clean-abap/CleanABAP.md

@@ -4660,15 +4660,7 @@ ENDMETHOD.
 
 > [Clean ABAP](#clean-abap) > [Content](#content) > [Testing](#testing) > [Injection](#injection) > [This section](#exploit-the-test-tools)
 
-In general, a clean programming style will let you do much of the work 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 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 environment (`CL_CDS_TEST_ENVIRONMENT`) to test your CDS views.
-
-A list of the available frameworks with examples can be found in [this repository](https://github.com/sautermi0/ABAPTestIsolationDemo). The repository might not be completely compliant with the CleanABAP-style guide, it only provides examples to help with test isolation tools.
+In general, a clean programming style will let you do much of the work with standard ABAP unit tests and test doubles. A list of the available frameworks with examples can be found in [this repository](https://github.com/SAP-samples/abap-test-isolation-examples). The repository might not be completely compliant with the CleanABAP-style guide, it only provides examples to help with test isolation tools.
 
 #### Use test seams as temporary workaround