> If the
> implementation of a model is
> wrong it isn't the job of the controller spec to
> report the failure.
> It's the job of the model spec or an integration
> test (if its an
> integration related issue) to report the failure.
It seems that it would be very easy to change a model,
thereby b
My first email sounded more certain that I intended.
I'm trying to work out my own views by throwing out
ideas in a peer review
fashion.
> The integration test will die if you broke
> functionality.
I'm curious what you mean by 'integration test'.
With regards to rails, are your integration te
>> The thing is that, ideally, you don't want to have to make changes to
>> the tests for object A when you're refactoring B.
>>
>> WDYT?
> Yeah, I buy that. Not everyone does though. Or at least not everyone
> feels that it's a particularly important goal.
I think the fear many of us classicis
> If you were to rename deposit to credit, and withdraw to debit
I'm more concerned with adding a parameter or changing the default value of a
parameter. My fear is that given enough time and size there will be a fair
number of inconsistent mocks or mocks that aren't doing any real testing. It
>because if you have integration tests covering everything,
>then you'll know pretty quickly when your tests aren't up to par.
If we have integration tests that cover everything then why have another set of
tests? At that point wouldn't it simply be duplication and wouldn't it create
more work
> Jay - are you familiar with Acceptance Test Driven
> Development/Planning and/or Test Driven Development?
I am with TDD and Acceptance testing (not sure if this is the same as
Acceptance Test Driven Development) . I use a more classic approach to use
Martin Fowler's terminology which is why I
I'm starting a new project and I want to try writing the client first. I.e. I
want to write my 'views' first and I would like to mock out all the models in
such a way that I can run the site and browse it with the mocked out models. Is
it easy to use rspec's mocking for this sort of thing and ha
I apologize, I oversimplified for the sake of brevity. We have most of the
models written but there are some pieces than aren't and won't be written in
the near future. I wanted to mock them out in some form so we can implement
those portions of the views. Things like certain features of the sid
sorry about that, I have no idea how that happened. It looked fine in yahoo
mail before I sent it :/
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.y
How do I use the ruby debugger with a specific test (not the whole spec file)?
I want to do something like this.
$ rdebug spec/models/user_spec.rb -s "should error if not new_record"
Looking for last
In all of my controller specs I have tests that look something like this.
it "should require login" do
get :edit, :id => '7'
response.should redirect_to(new_session_path)
end
I'd like to move this to a shared example, but the request call (get() or
post()) varies with each example. Is there
I use a lot of nested describe blocks and am wondering if there is a way to run
a specific describe block similar to the -e option for running specific
examples.
Jay
Looking for last minute shopping
example, 0 failures
- Original Message
From: James Deville <[EMAIL PROTECTED]>
To: rspec-users
Sent: Tuesday, March 11, 2008 9:26:13 PM
Subject: Re: [rspec-users] running a specific describe block
the -e option should run a describe block if the string passed matches
a desc
13 matches
Mail list logo
