diff --git a/docs/extensions/civix.md b/docs/extensions/civix.md
index 4b56df43fb7f3c84ddf0876e92b806275803b565..16cef9b9268058c0d040da848cd090e6d26e2ba7 100644
--- a/docs/extensions/civix.md
+++ b/docs/extensions/civix.md
@@ -63,13 +63,10 @@ There are many different features that you can add to a module-extension at your
 
 ### Add a unit-test class {:#generate-test}
 
-Unit-testing is essential to maintain quality-control over your extension. When developing a test case for a CiviCRM extension, it is useful to run the test case within an active, clean CiviCRM environment. The combined CiviCRM `civix` testing tools will automate this as long as you follow a few basic conventions.
+Unit-testing is essential to maintain quality-control over your extension. Ideally you write unit tests as you write your main code - this also helps you to writer cleaner, testable code. When developing a test case for a CiviCRM extension, it is useful to run the test case within an active, clean CiviCRM environment. The combined CiviCRM `civix` testing tools will automate this as long as you follow a few basic conventions.
 
 The following steps will create and run a test in your extension.
 
-!!! note
-    Before preparing unit-tests with extensions, you must first [configure you personal testing sandbox](https://wiki.civicrm.org/confluence/display/CRM/Setting+up+your+personal+testing+sandbox+HOWTO) and enable your extension on the sandbox. 
-
 Explore the full options with:
 
 ```bash
@@ -92,7 +89,8 @@ To make sure you can run the test civix needs to know where the CiviCRM base ins
 The skeletal test class does not do anything useful. For more details on how to write a test class:
 
 -   Read [PHP Unit Manual: Writing Tests for PHPUnit.](https://phpunit.de/manual/current/en/writing-tests-for-phpunit.html).
--   Review the example code in [org.civicrm.exampletests](https://github.com/totten/org.civicrm.exampletests).
+-   For more about testing in the CiviCRM environment see our [testing documentation](https://docs.civicrm.org/dev/en/latest/testing/)
+
 
 To run the tests see the instructions [for running PHPUnit tests](../testing/phpunit.md#running-tests).