Hi Matt,

On Sep 21, 4:13 am, Matt Jones <[email protected]> wrote:
> It seems like an interesting idea, but given the amount that's built  
> in with Hobo, it also smells a lot like testing the framework instead  
> of the user code.

I'm trying to be careful not to test the framework, but it's often
difficult to find the right balance.

> Even changing something simple (permissions on  
> Widget, for instance) will mean a line or two of changes to the code  
> and several times that to the tests.

Yeah, that thought has occurred to me - I'm hoping to make the test
fairly DRY so that changes should be minimal.

> Also, the hobo_model_resource  
> generator doesn't really have enough information to generate good  
> tests - what if the first thing I plan to do is change auto_actions  
> to :none and add auto_actions_for :something_else, :all? The generator  
> doesn't know that, and now I've got a ton of tests that aren't really  
> useful.

An approach I've been thinking about is to include scenarios for
testing each disabled auto_action but have them commented out
initially. So if you remove :new, then you delete the scenario 'Users
should be able to create new widgets' and uncomment the scenario
'Users are not allowed to create new widgets'.

> Finally, most of this code seems like it belongs more in a framework-
> level integration test, something that I keep meaning to post about...

I think both could happily co-exist. I'm hoping that the Cucumber
stuff will be more focused on business rules and UI.

Thanks for all the feedback, it's given me a few things to think
about.

BDD and Hobo come from two very different philosophies so it's
challenging to combine them!

Andy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Hobo 
Users" 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/hobousers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to