On 29 Jul 2007, at 12:54, Chris McGrath wrote:
Stories are good, code is better :) I think having some high level
statements about what merb will and will not do/provide for plugins
and testing frameworks agreed would be a good start and stories would
be one way of getting to them.
Replying to my own mail :)
I've had a look at the rspec_on_rails plugin in mrblog (is this the
right place?) and test_spec_on_rails from it's repo. My initial
impressions are there are several things merb should do for a test
harness:
1. Load the test database
2. Load the app files
3. Provide a FakeRequest
4. Provide MultiPart functionality
This seems to be the common stuff between the two plugins at the moment.
1 & 2 are concerned with merb initialization and i'm unsure what the
best way of handling this is.
re 3 & 4. I called the FakeRequest MockRequest yesterday, this is a
bad name as it's not a mock :). I'd like to add in a Merb::Test
namespace and have Merb::Test::FakeRequest and Merb::Test::MultiPart
for the plugins to use.
Chris
_______________________________________________
Merb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/merb-devel
