On Aug 2, 2008, at 4:43 PM, Luis Lavena wrote:
On Sat, Aug 2, 2008 at 9:04 PM, Mark Wilden <[EMAIL PROTECTED]>
wrote:
spec_server is one of the hidden gems of the RSpec world. It's not
completely a slam-dunk to use, and I know people who don't use it
because of
various problems, but it's wo
Hello list,
I'm trying to setup some shared specs to describe a CRUD controller
and want to reuse the logic in it.
I'm basing most of the examples in latest David's post about it [1]
The thing is that looking at the mailing list I couldn't find a
cleaner way to set the model that will be used in
On Sat, Aug 2, 2008 at 1:43 PM, Luis Lavena <[EMAIL PROTECTED]> wrote:
> One is the lack of possiblity to actually quit gracefully (they need
> to trap INT and properly stop the DRb server.
I just do rake spec:server:stop. This is necessary before running rake spec,
for instance, since rake spec
On Sat, Aug 2, 2008 at 9:04 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
> spec_server is one of the hidden gems of the RSpec world. It's not
> completely a slam-dunk to use, and I know people who don't use it because of
> various problems, but it's worth working through those problems, especially
>
spec_server is one of the hidden gems of the RSpec world. It's not
completely a slam-dunk to use, and I know people who don't use it because of
various problems, but it's worth working through those problems, especially
if you do T/BDD.
I've set up a vim script that runs just the current spec, whe
Exactly the kind of monkey patch I was looking for - thanks Luis !
I also saw you could edit the spec_server file to make
if options[:daemon]
into
if options[:daemon] and false or something similar, but a no touch
solution like yours is nice, and thanks for the Ctrl-Break tip.
D
Luis Lavena
On Sat, Aug 2, 2008 at 6:22 PM, Dean Radcliffe <[EMAIL PROTECTED]> wrote:
> Really tired of 30 second startup times to run Test::Unit tests, I would
> give my left pinky for a solution to running spec_server on windows. Is
> there some monkey patch that can avoid daemonizing the process
> altogeth
Really tired of 30 second startup times to run Test::Unit tests, I would
give my left pinky for a solution to running spec_server on windows. Is
there some monkey patch that can avoid daemonizing the process
altogether (Im fine if it runs as any kind of process at all). TIA.
Error below - I have op
On Sat, Aug 2, 2008 at 8:10 AM, Mikel Lindsaar <[EMAIL PROTECTED]> wrote:
> Heya all,
>
> I have an interesting case that I would like to bounce off the list.
>
> I have a separate thread going in ruby-talk about Timeout.timeout
> still running after the timeout specified. The spec on this has bee
Heya all,
I have an interesting case that I would like to bounce off the list.
I have a separate thread going in ruby-talk about Timeout.timeout
still running after the timeout specified. The spec on this has been
the classic 'I didn't write it, so I won't spec it' and so using mocks
and stubs.
10 matches
Mail list logo
