Does anyone have any insight into testing capistrano tasks? More
specifically, I'm looking to add regression tests to this package, which
adds database backup tasks to capistrano:
http://github.com/smtlaissezfaire/cap_db_dump/tree/master
Scott
__
Pelle Braendgaard wrote:
> I have made a fix to fixture scenarios which fixes that particular
> problem. I've made it available here:
>
> http://github.com/pelle/fixture-scenarios/tree/master
It works!
Thank you very, very much, Pelle.
Giuseppe
--
Posted via http://www.ruby-forum.com/.
On 27/01/2009, at 4:06 AM, rspec-users-requ...@rubyforge.org wrote:
Pat:
Put the describe in the module, and take advantage of Ruby's lookup
semantics:
module Foo
module Baz
describe Class1 do
...
Thanks for that beautifully simple suggestion! Thanks also to
Nick Hoffman
for
Mark Wilden wrote:
>
>
> The thing is that the Ruby idiom is to avoid unnecessary returns.
> Because of this, using them actually makes code harder to read,
> because you have to read it more carefully to see if they're being
> used for a legitimate reason.
If the method is short, the code simp
On 25/01/2009, at 9:56 PM, Stuart Hungerford wrote:
Hi,
I've got a set of classes in nested Ruby modules which I'm using
rspec to specify:
module Foo
module Baz
class C1 ... end
class C2 ... end
end
end
To specify C2 behaviour I need to create a bunch of C1 instances:
On Mon, Jan 26, 2009 at 9:06 AM, James Byrne wrote:
>
> I prefer the style of explicit returns. It makes intent unambiguous.
>
The thing is that the Ruby idiom is to avoid unnecessary returns. Because of
this, using them actually makes code harder to read, because you have to
read it more caref
Mark Wilden wrote:
> On Mon, Jan 26, 2009 at 7:23 AM, James Byrne
> wrote:
>
> This has nothing to do with your question - just a style suggestion:
>
> effective_from <= time_now and (superseded_after.nil? or
> superseded_after = time_now)
>
> No need to use 'return'. And you don't want to
On Mon, Jan 26, 2009 at 7:23 AM, James Byrne wrote:
> return true if (effective_from <= time_now and
> (not superseded_after or superseded_after >= time_now
> ))
> return false
>
This has nothing to do with your question - just a style suggestion:
effective_from <=
In tracking down a bug in AuthLogic I realized that I had made the same
error in one of my libraries. Knowing what the error was made creating
a test to expose it (using cucumber) rather trivial. However, it has
occurred to me that this sort of issue is far more subtle than I first
appreciated.
