Skip to content
This repository
Browse code

updated documentation w/ mention of CI_REPORTS

git-svn-id: http://svn.caldersphere.net/svn/main/rubyforge/ci_reporter/trunk@71 b03c2d0b-2f10-0410-a2f9-fc8001506dfa
  • Loading branch information...
commit cbe1c35c56c92ae21b329e7c6612447faa8d985d 1 parent f02e44c
Nick Sieger authored February 27, 2007

Showing 1 changed file with 3 additions and 1 deletion. Show diff stats Hide diff stats

  1. 4  README.txt
4  README.txt
@@ -33,9 +33,11 @@ CI::Reporter works best with projects that use a +Rakefile+ along with the stand
33 33
 
34 34
     rake ci:setup:testunit test
35 35
 
  36
+Report files are written, by default, to the <code>test/reports</code> or <code>spec/reports</code> subdirectory of your project.  If you wish to customize the location, simply set the environment variable CI_REPORTS (either in the environment, on the Rake command line, or in your Rakefile) to the location where they should go.
  37
+
36 38
 == Advanced Usage
37 39
 
38  
-If for some reason you can't use the above technique to inject CI::Reporter, you'll have to do one of these:
  40
+If for some reason you can't use the above technique to inject CI::Reporter (e.g., you're not using Rake), you'll have to do one of these:
39 41
 
40 42
 1. If you're using <code>Test::Unit</code>, ensure the <code>ci/reporter/rake/test_unit_loader.rb</code> file is loaded or required at some point before the tests are run.
41 43
 2. If you're using +RSpec+, you'll need to pass the following arguments to the +spec+ command:

0 notes on commit cbe1c35

Please sign in to comment.
Something went wrong with that request. Please try again.