Sha256: 1b4162c4037e1f7f92a6240f3cded67e5d3ad0a6a2502661d2b6f365869673da

Contents?: true

Size: 1.73 KB

Versions: 1

Compression:

Stored size: 1.73 KB

Contents

= lab_bench

A browser-based runner for ruby Test::Unit tests.

== Usage

Install the gem:

<tt>gem install lab_bench</tt>

If you're using Rails 2.x, add this to config/environment.rb:

<tt>config.gem 'lab_bench'</tt>

Start the server in a new console / screen:

<tt>lab_bench_server</tt>

Send your browser to http://localhost:9020/ then run your tests like this:

<tt>rake test TESTOPTS="--runner=lab_bench"</tt>

== TODO

* Give me more context on the test suite (names of files being run, command line, project directory, etc)
* Trim dependencies, or break into two gems (client / server) so we can minimize the number of dependencies we pull into the test runner
* Rails 3 compatability
* Allow me to rerun a suite
* Allow me to rerun a test
* Allow me to rerun all failed tests within a suite
* Continuous rerunning of failed tests (like autotest)
* Rerunning of failed tests when files change (like autotests)
* Notifications for success and failure
* Limit the number of events buffered on the server

== Contributing to lab_bench
 
* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
* Fork the project
* Start a feature/bugfix branch
* Commit and push until you are happy with your contribution
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

== Copyright

Copyright (c) 2010 Bradley Buda. See LICENSE.txt for further details.

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
lab_bench-0.3.1 README.rdoc