I suppose, worst case, we could build virtual appliances on which to test them. Short of that, it'd take a truly impressive mock :)
On Thu, Jul 17, 2008 at 9:14 AM, Jamis Buck <[EMAIL PROTECTED]> wrote: > > I'm embarrassed to admit that there are no unit tests for the > deployment recipes, largely because I'm unable to figure out how to > test them. If anyone comes up with a framework for testing the > recipes, I'd love it. :) > > - Jamis > > On Jul 17, 2008, at 3:29 AM, Jonathan Share wrote: > > > > > Hi, > > > > A little bit of background. I'm using Capistrano on a non RoR project > > (I actually gave a presentation at EuroPython last week [1]). > > > > One of the few tasks I'm overriding is deploy:setup as I don't want > > the default directories created under the :shared_path. > > > > Looking into the task it would seem simple to make that set of > > directories configurable with a variable that defaults to the current > > set. This would allow me to achieve my desired behaviour through > > configuration rather than overriding (which feels much cleaner). > > > > Before submitting a patch that makes this change I want to write a > > test for the current behaviour. I can't find an existing test for this > > and so tried adding a new one, however when I require > > 'capistrano/recipes/deploy' I get an error. I assume I need to load > > this in a special way to be able to run it's tasks. Any hints as to > > where to start? > > > > Thanks in advance > > > > Jon > > > > [1] > http://my.opera.com/WebApplications/blog/2008/07/14/slides-from-europython08 > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
