diff --git a/BUILDING.md b/BUILDING.md
index ed12a451f2e..18bb8d443c4 100644
--- a/BUILDING.md
+++ b/BUILDING.md
@@ -134,6 +134,15 @@ or embedding APIs, you should run JRuby's Java-based unit tests via
 mvn -Ptest
 ```
 
+On travis the following tests will run
+
+```
+mvn -Ptest
+mvn -Prake -Dtask=test:extended
+mvn -Prake -Dtask=spec:ci\_interpreted\_travis
+mvn -Ptruffle
+```
+
 There are some maven integration tests (i.e. consistency test if all gems are included, osgi test, etc) for the various distributions of JRuby which can be invoked with
 
 ```
diff --git a/docs/README.test.md b/docs/README.test.md
deleted file mode 100644
index 045f3f9d252..00000000000
--- a/docs/README.test.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# Writing Tests
-
-1. There are actually *4* core test suites:
-
-   a) `org.jruby.test.MainTestSuite`, a suite of pure-java tests;
-
-   b) `org.jruby.test.TestUnitTestSuite`, which runs a suite of files named
-   one-per-line in `test/jruby_index` (and other `test/*_index` files).
-   Note: some are commented out.
-
-   c) `Rubyspecs`, a recent point-in-time copy of [RubySpec](http://rubyspec.org)
-   project. The specs
-   are written in `rspec `format and aim to test conformance of JRuby
-   against the Ruby specification.
-
-   d) MRI's own tests, synced periodically. The tests are run with
-   `rake test:mri19` and known failing tests are marked as such in 
-   excludes files under `test/externals/ruby1.9/excludes`.
-
-2. If you'd like to contribute new tests, we'd prefer you write them via the
-`rubyspecs` project.  If the tests are very specific to JRuby (like Java
-Integration) we prefer writing `rspec`s under our `specs` directory.
-
-3. We're also interested in running tests for other ruby software suites; if
-you want to grab your favorite ruby software and run its own tests under JRuby
-and report to the mailing list at `dev@jruby.codehaus.org`, that would be great.
-
-4. Please file any and all patches in [Github issues](https://github.com/jruby/jruby/issues)
-
-# Running Tests
-
-Using ant, type
-
-    ant test
-
-The three test suites should be run in order.
-
-To run rubyspecs, type
-
-    ant spec
-
-A slightly shorter run we run frequently is:
-
-    ant spec-short
-
-The rubyspecs will be fetched over the net, and then executed.
-
-To run an individual test:
-
-1. run `ant install-dev-gems` which will install `bin/rspec` for use.
-2. run `ant compile-test` to compile the java fixtures (you don't need to wait for the tests to finish) then test as normal with `bin/rspec spec/path-to-spec`