diff --git a/docs/Native Tests.md b/docs/Native Tests.md
deleted file mode 100644
index 3c6f10a103..0000000000
--- a/docs/Native Tests.md	
+++ /dev/null
@@ -1,9 +0,0 @@
-# Native Code Testing Guide
-
-"Native" tests are tests which validate the native C/C++ function calls into the system library.  To run ONLY the native tests, it is assumed that you have completed the process in the README.md, and have run `source monad-docker.sh`.
-
-From the scripts directory, run `monad-run make -j native-tests`.  This will output an xml file to your scripts directory.
-
-# Creating new tests
-
-monad-linux/src/monad-native/src/tests is the test folder containing all the .cpp files.  you will need to `#include <gtest/gtest.h>` and follow gtest guidelines for creating your test suite.
\ No newline at end of file
diff --git a/docs/Testing.md b/docs/Testing.md
deleted file mode 100644
index 4ca2d6ce36..0000000000
--- a/docs/Testing.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# PowerShell for Linux
-
-This readme is targeted at PowerShell for Linux users looking to write test suites to ensure quality of PowerShell products.
-
-## Getting started
-
-These instructions assume Ubuntu 14.04 LTS. It is assumed that PowerShell for Linux is currently installed on the system.
-
-### Obtain PowerShell
-
-PowerShell is required to enable and run the test suites.
-
-### Testing technology
-
-Technology | Purpose
--------|------
-Pester | default cmdlet test framework
-xUnit | default C# test framework
-cppUnit | default C/C++ testing framework
-
-### Running the test suite
-
-Tests can be run from the `scripts` folder. If you are currently in `monad-linux/scripts`, then run `./build.sh make test` to run the complete tests suite.  The table below shows the commands to run for the various test products bundled with Powershell for Linux (the table assumes the current working directory is `monad-linux/scripts`).
-
-It is strongly recommended that before major changes are tested, that users run `./build.sh make clean cleanall prepare` to ensure the environment is completely clean.
-
-Technology | Run Method
-------|---------
-Pester | ./build.sh make pester-tests
-xUnit | ./build.sh make xunit-tests
-cppunit | ./build.sh make native-tests
-hashbang tests | ./build.sh make hashbang-tests
-
-within the `scripts` directory, you may also wish to run Pester tests on a single file.  This can be done easily using `./build.sh make {path/from/scripts/to/pester/test}` (E.g, `./build.sh make ../src/pester-test/Test-TESTFILE.Test.ps1`).
diff --git a/docs/xUnit Tests.md b/docs/xUnit Tests.md
deleted file mode 100644
index aab9d866d6..0000000000
--- a/docs/xUnit Tests.md	
+++ /dev/null
@@ -1 +0,0 @@
-#xUnit Testing Guide
\ No newline at end of file
diff --git a/docs/Pester Tests.md b/test/powershell/README.md
similarity index 100%
rename from docs/Pester Tests.md
rename to test/powershell/README.md