diff --git a/docs/testing/index.md b/docs/testing/index.md
index 1885e174e25c3dbcc87e6db336f62f73752135ab..f09bbc3ede9881884a8a65fb43b44b673cdb826e 100644
--- a/docs/testing/index.md
+++ b/docs/testing/index.md
@@ -3,6 +3,3 @@ The easiest way to get set up to run the automated tests is to use [buildkit](/t
 !!! info
     When writing new tests or making any changes make sure you run [civilint](/tools/civilint.md)
     to ensure your changes match our coding style.
-
-!!! tip
-    If you are using PhpStorm, you can [run the tests from within PhpStorm](/tools/phpstorm.md#testing) (which is especially helpful because you can set breakpoints and inspect variables while the tests run).
\ No newline at end of file
diff --git a/docs/testing/phpunit.md b/docs/testing/phpunit.md
index a8533b841ba31565a25eed4c59bee479bc5986fe..3e159bc0d48511525b114aea1c23f9059e16a1b4 100644
--- a/docs/testing/phpunit.md
+++ b/docs/testing/phpunit.md
@@ -32,6 +32,9 @@ environment variable `CIVICRM_UF` to "UnitTests" (eg. in `civicrm.settings.test.
     (creating system users etc.) your local build will be affected when running
     tests.
 
+!!! tip
+    If you are using PhpStorm, you can [run the tests from within PhpStorm](/tools/phpstorm.md#testing) (which is especially helpful because you can set breakpoints and inspect variables while the tests run).
+
 ## Running Tests
 
 From the CiviCRM root directory run the phpunit command, specifying a single