Fix broken links in test/ readme files (#985)

test/comparison-tests/conditionalRequire/README.md

@@ -3,9 +3,9 @@ This example shows how to do conditional compilation including requiring modules
 See the comments in `app.ts` and `webpack.config.js` for a quick overview of the process.
 
 Try defining and undefining the `DEBUG` constant in `webpack.config.js` and see out it affects
-[the output](expectedOutput/bundle.js).
+the outputs (e.g. [`expectedOutput-1.6/bundle.js`](expectedOutput-1.6/bundle.js)).
 
 More information can be found at these sites:
 - https://github.com/Microsoft/TypeScript/wiki/Modules#dynamic-module-loading-in-nodejs
 - https://github.com/webpack/docs/wiki/list-of-plugins#defineplugin
-- https://github.com/webpack/webpack/tree/master/examples/multi-compiler
+- https://github.com/webpack/webpack/tree/master/examples/multi-compiler

test/execution-tests/README.md

@@ -3,7 +3,7 @@
 This test pack is made up of a number of mini-typescript projects which include a test suite.  As part of the test run, each project is compiled and the test suite run using Karma. So this test pack is different from the comparison test pack in that it **executes the compiled code**. This test pack is useful for testing expected behaviour.  (It's also reassuring to see your
 code being executed.)
 
-These tests are executed more widely that the comparison tests; we aim to run these against each version of TypeScript defined in our CI build matrices. (Take a look at [`appveyor.yml`](appveyor.yml) and [`.travis.yml`](.travis.yml) for details.)
+These tests are executed more widely that the comparison tests; we aim to run these against each version of TypeScript defined in our CI build matrices. (Take a look at [`appveyor.yml`](../../appveyor.yml) and [`.travis.yml`](../../.travis.yml) for details.)
 
 ## Structure