Now implement and refractor and you're correctly doing BDD.
On 16/02/2008, at 12:11 AM, [EMAIL PROTECTED] wrote:
> test
> ___
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
___
On Fri, 15 Feb 2008 01:07:27 -0500, David Chelimsky wrote:
> The source of the bug was a patch that we applied a while back. This was
> after the 1.1.3 release, so if you're using 1.1.3 you're fine. If you're
> using trunk, go ahead and update and you should be fine now.
>
Thanks, I appreciate i
> You can reduce the frequency at which autotest checks for changes on
> your
> file system by adding an initialize hook in your ~/.autotest
> configuration:
If you are running Leopard, you might be interested in a hack a co-
worker of mine used to tame autotest. He replaced autotest's pollin
I seem to remember when I was running a previous version of rspec and
autotest that when a set of specs passed for some changed files, that all
of the specs would then be run automatically. Particularly when tests had
previously failed. It's not doing it now on trunk. Was I imagining this,
or i
On Feb 15, 2008, at 8:14 AM, Kiran1009 wrote:
>
> Hi,
>
> This is most USEFUL...
>
> http://www.oreillynet.com/pub/a/ruby/2007/08/09/behavior-driven-development-using-ruby-part-1.html
>
> Check this out...
Excellent pointer!! Thank you. I'll see if this series of articles can
be added to an rs
On Fri, Feb 15, 2008 at 10:27 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> D'oh! Let's try that again.
>
> behave
Austin "Chelimsky" Powers ?!
--
Rick DeNatale
My blog on Ruby
http://talklikeaduck.denhaven2.com/
___
rspec-users mailing list
rspe
Bug report from Scott Taylor on this:
http://rspec.lighthouseapp.com/projects/5645/tickets/274
> Hi All,
>
> I submitted a patch last week to fix a bug with --drb not working if
> it's specified in spec.opts, this causes autotest to run obscenely
> slowly out of the box on my machine.
>
> Please
D'oh! Let's try that again.
behave
On Fri, Feb 15, 2008 at 10:25 AM, Mike Vincent <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 15, 2008 at 9:11 AM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > test
>
> 1 tests, 0 assertions, 0 failures, 0 errors
>
>
>
On Fri, Feb 15, 2008 at 9:11 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> test
1 tests, 0 assertions, 0 failures, 0 errors
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
test
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Hi,
This is most USEFUL...
http://www.oreillynet.com/pub/a/ruby/2007/08/09/behavior-driven-development-using-ruby-part-1.html
Check this out...
Thanks&Regards.
Kiran.
Chuck Remes-3 wrote:
>
> I'm starting a new project which I would like to use as a learning
> opportunity for BDD. I've s
Thank you much.
On Fri, Feb 15, 2008 at 12:07 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> The source of the bug was a patch that we applied a while back. This
> was after the 1.1.3 release, so if you're using 1.1.3 you're fine. If
> you're using trunk, go ahead and update and you should be
I am using RSpec 1.1.3 with ZenTest-3.9.1 and I wanted to share my set up.
If your cpu is at 100% when autotest is running and the fan noise is getting
too much, don't worry there's something you can do.
You can reduce the frequency at which autotest checks for changes on your
file system by add
13 matches
Mail list logo