just a quick clarification, we are not breaking the controller/helper
specs, just not generating them and not encouraging people to use them
;)

-Matt

On Wed, Oct 29, 2008 at 9:03 PM, Mirko <[EMAIL PROTECTED]> wrote:
>
> I'd also prefer to keep the existing controller, view, and helper
> specs around. The new request specs sound great for functional
> testing, but I'd like to be able to still write unit tests for the
> various application layers.
>
> -Mirko
>
> On Oct 29, 1:02 am, Ashley Moran <[EMAIL PROTECTED]>
> wrote:
>> On Oct 29, 2008, at 4:21 am, Yehuda Katz wrote:
>>
>> > As of RC1, the notion of "controller", "view" and "helper" specs are
>> > deprecated in favor of "request" specs, which test the responses for
>> > a given request.
>>
>> I'd like to vote in favour of these being maintained, even if they're
>> not the "recommended offical way" to write specs.
>>
>> There's a large contingency of BDDers who prefer to maintain
>> acceptance tests in another tool (Story Runner or Cucumber), and use
>> RSpec for lower level things, such as controllers and helpers.
>> Deprecating the isolated spec formats gives us two ways of solving one
>> problem and none of solving the other.
>>
>> Ashley
>>
>> --http://www.patchspace.co.uk/http://aviewfromafar.net/
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to