@@ -48,34 +48,47 @@ See the [Wiki](http://github.com/rubyworks/test/wiki) for further details.
4848
4949## Usage
5050
51- There are a few ways to run tests. First, there is a command line tool:
51+ There are a few ways to run tests. First, there is the command line tool
52+ e.g.
5253
53- $ rubytest
54+ $ rubytest test/test_*.rb
5455
55- The command line tool takes various options, use ` --help ` to see them.
56- Be sure to load in your test framework or framework's Ruby Test adapter.
56+ The command line tool takes various options, use ` -h/--help ` to see them.
5757
58- Preconfigurations can be defined in a ` .test ` file, e.g.
58+ When running tests, you need to be sure to load in your test framework
59+ or your framework's RubyTest adapter. This is usually done via a helper
60+ script in the test files, but might also be done via command line options,
61+ e.g.
5962
60- Test.run 'default' do |r|
61- r.format = 'progress'
62- r.requires << 'lemon'
63- r.files << 'test/*_case.rb'
64- end
63+ $ rubytest -r lemon -r ae test/test_*.rb
6564
66- There is also a 'rubytest/autorun.rb' library script that can be loaded which
67- creates an ` at_exit ` runner, for which ` test.rb ` provides a nice shortcut:
65+ RubyTest supports [ dotopts] ( http://rubyworks.github.com/dotopts ) out of the
66+ box, so it easy to setup reusable options. For example, a ` .option ` file
67+ entry might be:
6868
69- $ ruby -r test
69+ rubytest
70+ -f progress
71+ -r spectroscope
72+ -r rspecial
73+ spec/spec_*.rb
7074
71- There is also a Rake task.
75+ There is also a Rake task. In your Rakefile,
7276
7377 require 'rubytest/rake'
7478
75- Test::Rake::TestTask.new
79+ Test::Rake::TestTask.new do |run|
80+ require 'lemon'
81+ run.files << 'test/test_*.rb'
82+ end
7683
7784A Detroit plugin is in the works and should be available soon.
7885
86+ See the Wiki for more information on the different ways to run tests.
87+
88+
89+ Notice the use of ` Test.configure ` which is .
90+
91+
7992
8093## Installation
8194
0 commit comments