Update readme to markdown and expand.

2 files changed, 39 insertions, 7 deletions

diff --git a/testsuite/README b/testsuite/README
deleted file mode 100644
index 9198eb3c31..0000000000
--- a/testsuite/README
+++ /dev/null
@@ -1,7 +0,0 @@
-GHC Testsuite Readme
---------------------
-
-For testsuite documentation, please see:
-
-    http://hackage.haskell.org/trac/ghc/wiki/Building/RunningTests
-
diff --git a/testsuite/README.md b/testsuite/README.md
new file mode 100644
index 0000000000..9b52e305a5
--- /dev/null
+++ b/testsuite/README.md
@@ -0,0 +1,39 @@
+GHC Testsuite Readme
+====================
+
+For the full testsuite documentation, please see [here][1].
+
+## Quick Guide
+
+Commands to run testsuite:
+
+ * Full testsuite: `make`
+ * Using more threads: `make THREADS=12`
+ * Reduced (fast) testsuite: `make fast`
+ * Run a specific test: `make TEST=tc054`
+ * Test a specific 'way': `make WAY=optllvm`
+ * Test a specifc stage of GHC: `make stage=1`
+ * Pass in extra GHC options: `make EXTRA_HC_OPTS=-fvectorize`
+
+You can also change directory to a specific test folder to run that
+individual test or group of tests. For example:
+
+``` .sh
+$ cd tests/array
+$ make
+```
+
+## Testsuite Ways
+
+The testsuite can be run in a variety of 'ways'. This concept refers
+to different ways that GHC can compile the code. For example, using
+the native code generator (`-fasm`) is one way, while using the LLVM
+code generator (`-fllvm`) is another way.
+
+The various ways that GHC supports are defined in `config/ghc`
+
+## Adding Tests
+
+Please see the more extensive documentation [here][1].
+
+  [1]: http://hackage.haskell.org/trac/ghc/wiki/Building/RunningTests