buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor Hugo Borja (JIRA)" <>
Subject [jira] Commented: (BUILDR-29) Run RSpec specs with JRuby
Date Wed, 02 Apr 2008 23:34:24 GMT


Victor Hugo Borja commented on BUILDR-29:

Nick's rspec framework is in trunk now, searches for src/spec/ruby/**/*_spec.rb. 
JtestR is still a fast-moving target, so I'll wait a little before integrating it with buildr.

> Run RSpec specs with JRuby
> --------------------------
>                 Key: BUILDR-29
>                 URL:
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Test frameworks
>    Affects Versions: 1.3
>            Reporter: Nick Sieger
>            Assignee: Victor Hugo Borja
>             Fix For: 1.3
>         Attachments: buildr_framework.rb
> Attached is a test framework I wrote that allows me to write RSpec specs that test Java
> If Buildr is run under MRI, JRuby is downloaded as a dependency and launched to run the
> If Buildr is run under JRuby, JRuby will launch a sub-vm of itself, including the project
classpath but using the same JRuby version that was used to launch Buildr.
> Note the following features and/or limitations:
> * No specs for this currently exist; they'll need to be written if you want the coverage.
I probably won't write them (for now) :)
> * Assumes project specs are in the "spec" directory. You may want this to be customized.
> * Runs specs in "specdoc" mode (hard-coded). Choosing a formatter would be another possible
> * Allows a {{SPEC}} environment variable to be set or passed on the command-line to specifiy
a single spec to run (just like the RSpec rake task)
> * Allows {{:required_gems}} as an option to be passed to the "test" clause of the project,
which will ensure that gems are present before running (installing them if necessary) before
running specs. There is currently no way to specify gem version.
> * Uses ci_reporter to generate JUnit-like XML reports; assumes that they may be useful
(perhaps in conjunction with the junit:report task); but it's not strictly necessary.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message