Aslak,
I have admit, when I saw the option: testunit, I was just curious as
to what it would do
.assumed it would be something additional...I guess
we have some critical legacy unit/integration tests that will probably
survive forever.
but going forward everything is rspec and cucumber
in cuc
> I tried to reproducevery strange
> I'm back to being confused again.
> ..as to why of course
>
> in my blank, demo project I ran
> > script/generate --webrat --rspec --testunit
> it does produce a different env.rb file
> -- without a "require cucumber/rails/rspec" statement
>
> but the be_tru
I tried to reproducevery strange
I'm back to being confused again.
..as to why of course
in my blank, demo project I ran
> script/generate --webrat --rspec --testunit
it does produce a different env.rb file
-- without a "require cucumber/rails/rspec" statement
but the be_true still works. ???
I figured it out last night.
...sorry I didn't post then
I created a blank rails project and used:
$ script/generate --webrat --rspec
then compared the features/support/env.rb; mine was missing:
require 'cucumber/rails/rspec'
after adding that statement, the be_true and be_falses worked fine
the
On Wed, Dec 23, 2009 at 3:44 PM, Ronald Chaplin wrote:
> So I'm going through the rspec book right now, and get to page 72, as it
> introduces Spec::Mocks::Methods#as_null_object . In the book, it doesn't
> describe how it operates, or much detail about it other than it tells to
> expect certain
So I'm going through the rspec book right now, and get to page 72, as it
introduces Spec::Mocks::Methods#as_null_object . In the book, it doesn't
describe how it operates, or much detail about it other than it tells to
expect certain data, and ignore the rest.
ri Spec::Mocks::Methods#as_null_objec
> I agree
>
> I did notice that my feature/support/my_env.rb (custom) had:
> require 'spec'
> require 'spec/rails'
>
> so I changed first line
> require 'spec/autorun'
>
>
You shouldn't do that. You don't want the RSpec runner to run when you're
using Cucumber.
In fact, you shouldn't do any RSp
I agree
I did notice that my feature/support/my_env.rb (custom) had:
require 'spec'
require 'spec/rails'
so I changed first line
require 'spec/autorun'
in keeping with http://wiki.github.com/dchelimsky/rspec/configgem-for-rails
seems to me that really should do it, but it doesn't work.
