I'm using it in my tests, so no harm in calling the internal API anyway.
Thanks for the excellent library.
cheers,
Brett
On 24/03/2010, at 2:53 AM, Jeff Forcier wrote:
This stuff isn't part of the API, so keep in mind that it may get
moved around; but it will get added to the API at a
I initially tried to use unittest with fabric but got errors - I think related
to the stdout, stderr, so then I stuck my testing into a fabfile that tests
other fabfile functions, but that's gettting a bit unwieldy as it gets bigger.
Does anyone have good strategies for unittesting fabfile
That's exciting.
What would make me even more excited is if you pushed
http://code.fabfile.org/issues/show/189 into 1.0
It's my biggest irritation at the moment. How to test if a server has already
been setup without storing state on the client.
At the moment I change ssh port and add in a
I'm not sure why you wouldn't just use roles but fabric sets the hosts before
the functions are run so if you're trying to alter what hosts things run on at
a function level you should use @hosts decorator or more likely for what you
want the `with settings` context manager.
ie with
