On 17 May 2010, at 11:38, David Chelimsky wrote:
On May 16, 2010, at 11:10 PM, Scott Taylor wrote:
On May 16, 2010, at 8:13 PM, David Chelimsky wrote:
On May 16, 2010, at 12:54 PM, Scott Taylor wrote:
Hey all,
I'm wondering if anyone has any experience with an automated test-
case gene
Dear list,
Today I am working through the simple tutorial here:
http://wiki.github.com/aslakhellesoy/cucumber/ruby-on-rails
It has me install Cucumber-Rails and then create a feature.
Then I watch the feature fail when I run
rake cucumber
Then I watch the feature pass after I implement some c
On May 19, 2010, at 4:45 PM, Myron Marston wrote:
> The new tagging support in rspec 2 looks fantastic, but I don't think
> we're ready to upgrade to rspec 2 yet, especially since it's still in
> beta.
>
> How does the directory approach work with rspec 1? (And feel free to
> point me to a blog
The new tagging support in rspec 2 looks fantastic, but I don't think
we're ready to upgrade to rspec 2 yet, especially since it's still in
beta.
How does the directory approach work with rspec 1? (And feel free to
point me to a blog post or wiki entry that documents this--I've done
some googling
On May 19, 2010, at 4:11 PM, Myron Marston wrote:
> On my current rails project we're using both rspec and cucumber.
> We've been diligent about keeping our specs as true unit tests, using
> nulldb and mocking/stubbing to disconnect the specs from the database
> and keep each spec focused on the c
On my current rails project we're using both rspec and cucumber.
We've been diligent about keeping our specs as true unit tests, using
nulldb and mocking/stubbing to disconnect the specs from the database
and keep each spec focused on the class/method under test. Our
cucumber features are integrat
