Skip to content

Commit

Permalink
updated documentation w/ mention of CI_REPORTS
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.caldersphere.net/svn/main/rubyforge/ci_reporter/trunk@71 b03c2d0b-2f10-0410-a2f9-fc8001506dfa
  • Loading branch information
nicksieger committed Feb 27, 2007
1 parent f02e44c commit cbe1c35
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.txt
Expand Up @@ -33,9 +33,11 @@ CI::Reporter works best with projects that use a +Rakefile+ along with the stand

rake ci:setup:testunit test

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.

== Advanced Usage

If for some reason you can't use the above technique to inject CI::Reporter, you'll have to do one of these:
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:

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.
2. If you're using +RSpec+, you'll need to pass the following arguments to the +spec+ command:
Expand Down

0 comments on commit cbe1c35

Please sign in to comment.