On Sep 17, 2009, at 11:04 AM, Andy Waite wrote:
> > Here's a preview of what I'm working on. The intention is that when > you run > > script/generate hobo_model_resource widget name:string > > Then a feature file like the ones below gets automatically generated, > reflecting the default Hobo behaviour. > > Then when you begin to customise the behaviour, you just edit the > scenarios as appropriate. > > Andy 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. 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. 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. Finally, most of this code seems like it belongs more in a framework- level integration test, something that I keep meaning to post about... Essentially, the goal of an integration test suite for Hobo would be to have several "test bed" apps (kind of like Agility is now), with tests in those apps that cover the features of Hobo. I've got a smaller app that may get used for that purpose, once I get the official OK to reuse the code. --Matt Jones --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
