Err, not really talking about the same thing here. Selenium, Squish, Windmill can be considered unittests for *sites*. As cool and useful as that is, first I'd like to have a component that can just test a view. I don't really see how you would make any of the above suites work around the controllers on it's own (e.g. how would windmill supply you with a pregenerated controller *output* instead of controller *input*).
Think about it this way - you have a fancy view that has to fit some fancy data and do some display magic (or generate a form) based on the content, but the controller code that generates the tables is still under development. Not talking about user interaction/simulation here, just plain presentation. Sort of a sanity check for the view to match back to designer specs. On Mar 30, 5:42 pm, mdipierro <[email protected]> wrote: > we should look into windmill. It really impressed me at PyCon. > > On Mar 30, 10:39 am, AchipA <[email protected]> wrote: > > > While writing some unittests for my controllers, it occured to me that > > it would be pretty handy to have a unittest like thing for views. So, > > the use-case would be to construct a controller response (even > > manually if it's easier) and then preview the template with the given > > test data. I'm a bit unsure about how such a thing could be properly > > validated, but IMO it sure would speed up view development. Of course > > you can do this already by making dummy controllers specifically for > > this purpose, I'm just thinking that maybe it could be made more > > elegant. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
