On Thu, Feb 4, 2010 at 00:12, David Mitchell wrote:
> What is the 'best practice' way to structure RSpec code and documentation
> when testing a very large project, where the RSpec code base has to be
> maintained and extended over a long period?
I don't mean to be glib, but my blink reaction is
On Thu, Feb 4, 2010 at 8:09 AM, J. B. Rainsberger
wrote:
> On Thu, Feb 4, 2010 at 00:12, David Mitchell wrote:
>
>> What is the 'best practice' way to structure RSpec code and documentation
>> when testing a very large project, where the RSpec code base has to be
>> maintained and extended over a
Is rSpec 2.0 going to be covered at all in the rSpec book, I'm expecting
delivery of the book as soon as it goes to print, so just curious.
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.
On Thu, Feb 4, 2010 at 8:47 AM, Stuart Corbishley wrote:
> Is rSpec 2.0 going to be covered at all in the rSpec book, I'm expecting
> delivery of the book as soon as it goes to print, so just curious.
Unfortunately, no. To cover rspec-2 in the book we'd have to push back
delivery by a few months,
On Thu, Feb 4, 2010 at 9:40 AM, David Chelimsky wrote:
> On Thu, Feb 4, 2010 at 8:09 AM, J. B. Rainsberger
> wrote:
>> On Thu, Feb 4, 2010 at 00:12, David Mitchell wrote:
>>
>>> What is the 'best practice' way to structure RSpec code and documentation
>>> when testing a very large project, where
David Chelimsky wrote:
> On Thu, Feb 4, 2010 at 8:47 AM, Stuart Corbishley
> wrote:
>> Is rSpec 2.0 going to be covered at all in the rSpec book, I'm expecting
>> delivery of the book as soon as it goes to print, so just curious.
>
> Unfortunately, no. To cover rspec-2 in the book we'd have to p
On 4 Feb 2010, at 14:09, J. B. Rainsberger wrote:
On Thu, Feb 4, 2010 at 00:12, David Mitchell
wrote:
What is the 'best practice' way to structure RSpec code and
documentation
when testing a very large project, where the RSpec code base has to
be
maintained and extended over a long per
Thanks for the response. That's an interesting approach. I will try
that and see how far I can get with it.
If my ruby chops were a little better, I suspect I could find a more
elegant solution. Any other ideas out there?
On 2/3/10, Matt Wynne wrote:
> One way would be to use an environment v
On Thu, Feb 4, 2010 at 12:35, Levi Conley wrote:
> Thanks for the response. That's an interesting approach. I will try
> that and see how far I can get with it.
>
> If my ruby chops were a little better, I suspect I could find a more
> elegant solution. Any other ideas out there?
It sounds lik
On Thu, Feb 4, 2010 at 09:40, David Chelimsky wrote:
> On Thu, Feb 4, 2010 at 8:09 AM, J. B. Rainsberger
> wrote:
>> On Thu, Feb 4, 2010 at 00:12, David Mitchell wrote:
>>
>>> What is the 'best practice' way to structure RSpec code and documentation
>>> when testing a very large project, where t
On Thu, 4 Feb 2010 09:51:08 -0500, you wrote:
>It's just a small battle in the never-ending war against the increase
>of entropy.
>
>It may seem hard, but remember the more you fight it the more you
>delay the heat death of the universe!
Actually, it's just the opposite: Any attempt to reduce lo
On Wed, Feb 3, 2010 at 8:41 PM, rogerdpack wrote:
>> spec-server was deprecated and removed a few versions back in favor of
>> spork, which works with rspec and test/unit AFAIK.
>
> Right, I was just wondering if there was something that pre-dated
> spork, but for test-unit shtuffs...spork does su
Hi
Just wondering if anyone knows why I am getting this error now ??
gem install rspec-rails --version 1.2.9 --no-ri --no-rdoc
**
Thank you for installing rspec-rails-1.2.9
If you are upgrading, do this in each of your rails apps
th
13 matches
Mail list logo
