[Ironruby-core] ironruby-rack gem
jschementi at gmail.com
Sun Apr 24 09:08:14 EDT 2011
There are two important parts to testing IronRuby-Rack:
First, we need to make sure IronRuby can run rack 1.2. This will be a subset of the tests as rack has tests for mongrel and thin, which we won't be able to run, but the webrick test is fair game. The rack tests are checked into external/languages/ruby/tests, as we used to run rack tests against IronRuby in CI. So just updating those tests and running them should be all that's required, and well see what bugs come out of that.
Second we need to actually test IronRuby-Rack: given a HttpRequest it creates a valid rack request, runs the request, and then takes the rack response and makes into a HttpResponse. We should thoroughly make sure that's unit tested, and the only way to do that is write the tests; the rack tests won't really help. Currently there are some unit tests and a test similar to rack's webrick test that use Cassini instead. For starters in testing the HttpRequest portion, we could give it a HttpRequest and run rack-lint to make sure it doesn't fuck anything up. But ideally we'll probably need tests exercising the entire rack spec.
On Apr 23, 2011, at 11:35 PM, Kevin Radcliffe <kevin.radcliffe at gmail.com> wrote:
> I may also be interested in contributing to move IronRuby.Rack toward rack-1.2.0 compatibility.
> I would imagine (but this could be totally wrong) that we would want to move more tests over from:
> Would this be a good approach?
> Where would be a good place for them, here?
> (Or pehaps a subdirectory off of that)
> If it isn't a good approach, what would be a better way to move toward 1.2.0 compatibility?
> Best Regards,
> Kevin Radcliffe
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironruby-core