Point readers to civi-test-run page from elsewhere

docs/testing/continuous-integration.md

@@ -35,5 +35,9 @@ codebase.
  
 Code-style is not checked on this build, but all upgrade and web tests are run.
 
+## Running the test suite locally
+
+You can use [civi-test-run](/tools/civi-test-run.md) locally to run a full standard CiviCRM Test suite.
+
 [jenkins-test-results]: https://test.civicrm.org/
 [testing-readme]: https://github.com/civicrm/civicrm-core/blob/master/tests/README.md

docs/testing/javascript.md

@@ -14,11 +14,7 @@ $ cd /path/to/civicrm
 $ npm test
 ```
 
-You can also run the karama tests as they would be run by Jenkins using the `civi-test-run` command
-
-```bash
-$ civi-test-run "<buildname>" "<civicrm version>" "<junitdir>" "karma"
-```
+You can also run the karama tests as they would be run by [Jenkins](/testing/continuous-integration.md) using [civi-test-run](/tools/civi-test-run.md).
 
 [karma]: https://karma-runner.github.io/1.0/index.html
 [jasmine]: https://jasmine.github.io/2.1/introduction.html

docs/testing/phpunit.md

@@ -52,18 +52,7 @@ $ env CIVICRM_UF=UnitTests phpunit4 ./tests/phpunit/api/v3/CaseTest.php --filter
     You can also specify tests in an environment variable `PHPUNIT_TESTS` (eg. `env PHPUNIT_TESTS="MyFirstTest::testFoo MySecondTest" phpunit EnvTests`
     Then run `phpunit4 ./tests/phpunit/EnvTests.php`.
 
-You can also optionally run a full standard CiviCRM Test suite by running `civi-test-run` as per example below
-
-```bash
-$ civi-test-run "<buildName>" "<civicrm version>" "<junit dir>" "<test-type>"
-```
-The test type is one of:
-
--  All: Run all standard CiviCRM Test Suites
--  phpunit-e2e - Run the E2E test suite
--  phpunit-civi - Run the Civi/ Test Suite
--  phpunit-api - Run the `api_v3` Test Suite
--  phpunit-crm - Run the `CRM` Test Suite
+You can also optionally use [civi-test-run](/tools/civi-test-run.md) to run a full standard CiviCRM Test suite.
 
 ## Writing Tests
 

docs/testing/upgrades.md

@@ -8,10 +8,4 @@ CMS-integration.
 
 Upgrade tests are run daily on the Jenkins [continuous integration](/testing/continuous-integration.md) server.
 
-## Local Upgrade Testing
-
-Locally you can run the same upgrade tests as Jenkins would using `civi-test-run` as per the following example
-
-```bash
-$ civi-test-run "<civibuildname>" "<civiversion>" "<junitdir>" "upgrade"
-```
+Locally you can use [civi-test-run](/tools/civi-test-run.md) to run the same upgrade tests as Jenkins would.