Permalink
Browse files

Convert TESTING to markdown. Copy edit it a bit.

  • Loading branch information...
r00k committed Jul 12, 2011
1 parent f10c7f8 commit 0ffb6874d089b8e49964fbc1cad529dcf8fc3949
Showing with 25 additions and 16 deletions.
  1. +25 −0 TESTING.md
  2. +0 −16 TESTING.rdoc
View
@@ -0,0 +1,25 @@
+Running the suite
+=================
+
+Since the notifier must run on many versions of Rails, running its test suite is slightly different than you may be used to.
+
+First execute the following command:
+
+ rake vendor_test_gems
+
+This command will download the various versions of Rails that the notifier must be tested against.
+
+Then, to start the suite, run
+
+ rake
+
+Note: do NOT use 'bundle exec rake'.
+
+For Maintainers
+================
+
+When developing the Hoptoad Notifier, be sure to use the integration test against an existing project on staging before pushing to master.
+
+ ./script/integration_test.rb <test project's api key> <staging server hostname>+
+
+ ./script/integration_test.rb <test project's api key> <staging server hostname> secure+
View
@@ -1,16 +0,0 @@
-= Running the suite
-
-Cannot run @bundle exec rake@ . Must use the non-bundled rake. If you have an
-alias run it like this:
-
-% \rake vendor_test_gems
-% \rake
-
-= For Maintainers:
-
-When developing the Hoptoad Notifier, be sure to use the integration test
-against an existing project on staging before pushing to master.
-
-+./script/integration_test.rb <test project's api key> <staging server hostname>+
-
-+./script/integration_test.rb <test project's api key> <staging server hostname> secure+

0 comments on commit 0ffb687

Please sign in to comment.