I've developed a module to include in ActiveRecord derived classes. Can I
test the module without having to tie it to a particular class? atm, I'm
including it in my User class and writing the tests in user_spec.rb, but I
don't like the idea of tying the module tests to those of the class.
I may
I'm finding that I'm writing sets of very similar scenarios to check access
permissions for each of my actions. Does anyone have suggestions on how to
dry this up:
Given an existing Account
And a logged in Admin
When the user visits account/manage
Then he should get access
Given an existing Acco
DD violations there? I personally don't mind the somewhat complex
steps because as Ben pointed out, the plain text stories are more manageable
this way and still very readable.
Neil M. Young wrote:
>
> I'm finding that I'm writing sets of very similar scenarios to check
>
I see that rails handles exceptions in stories by rendering public/500.html,
whereas in controller specs exceptions are re-raised. Is it possible to have
this same behaviour in stories so I can check the correct exceptions are
being raised?
--
View this message in context:
http://www.nabble.com/
sorry if this is documented somewhere, but do stories support colored output?
neither -c nor --color are working for me.
--
View this message in context:
http://www.nabble.com/colored-output-for-stories--tp15363648p15363648.html
Sent from the rspec-users mailing list archive at Nabble.com.
aslak hellesoy wrote:
>
> On Feb 8, 2008 9:50 PM, Neil M. Young <[EMAIL PROTECTED]> wrote:
>>
>> sorry if this is documented somewhere, but do stories support colored
>> output?
>> neither -c nor --color are working for me.
>
> It works for me. What&