Use absolute paths for internal links

docs/testing/continuous-integration.md

@@ -36,5 +36,4 @@ codebase.
 Code-style is not checked on this build, but all upgrade and web tests are run.
 
 [jenkins-test-results]: https://test.civicrm.org/
-[civilint]: dev-tools/civilint.md
 [testing-readme]: https://github.com/civicrm/civicrm-core/blob/master/tests/README.md

docs/testing/phpunit.md

@@ -91,5 +91,5 @@ rollback automatically at the end of the test.
     or change the database schema please be aware you may need to manually reset
     it.
 
-[buildkit]: ../tools/buildkit.md
+[buildkit]: /tools/buildkit
 [civi-test-class]: https://github.com/civicrm/org.civicrm.testapalooza/blob/master/civi-test.md

docs/testing/selinium.md

@@ -40,4 +40,4 @@ cd tools
 - [Selenium documentation](http://seleniumhq.org/docs/)
 - [Selenium reference](http://release.seleniumhq.org/selenium-core/1.0.1/reference.html)
 
-[buildkit]: ../tools/buildkit.md
+[buildkit]: /tools/buildkit

docs/testing/upgrades.md

@@ -11,5 +11,5 @@ Upgrade tests are run daily on the Jenkins [continuous integration][ci] server.
 If you are working on a core upgrade you can save some time and check out this
 handy [test-helper] to run upgraders from specific versions.
 
-[ci]: continuous-integration.md
+[ci]: /testing/continuous-integration
 [test-helper]: https://github.com/civicrm/civicrm-buildkit/blob/master/doc/daily-coding.md#upgrade-tests