From chad.humphries at gmail.com  Sat Nov  1 16:50:14 2008
From: chad.humphries at gmail.com (Chad Humphries)
Date: Sat, 1 Nov 2008 16:50:14 -0400
Subject: [rspec-devel] Pulling the story runner out of rspec/rspec-rails
In-Reply-To: <57c63afe0810300656l5c8f185bjb1c6dda9b27b0e61@mail.gmail.com>
References: <16f722280810300427l635a5116w1068a85270e3295f@mail.gmail.com>
	<57c63afe0810300656l5c8f185bjb1c6dda9b27b0e61@mail.gmail.com>
Message-ID: <16f722280811011350n2cbb7577t38c92f24dbcd7eea@mail.gmail.com>

My fork of RSpec has the story runner extracted.  I have a question
about the story runner gem though.   Is is to be more of a stand-alone
gem ala cucumber, or can it be dependent on RSpec?   I think I have an
approach working with a dependency on RSpec now.

--
Chad

On Thu, Oct 30, 2008 at 9:56 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Thu, Oct 30, 2008 at 6:27 AM, Chad Humphries
> <chad.humphries at gmail.com> wrote:
>> Hey again,
>>
>> I've been working on my fork of RSpec recently and I have removed
>> story runner a few different ways.  I can pull it out into it's own
>> gem fairly quickly, although the gem will require a little more of my
>> time to make it prim and proper for public consumption.  My question
>> is this, do you still want the story runner pulled out into a separate
>> gem?  I'm not interested into maintaining it long-term, but I do have
>> some time to take care of the extraction and hand off to whomever
>> would like to.
>
> This is definitely in the plan. I wasn't planning to tackle it until
> later this year, perhaps early '09, but if you can get it working and
> clean and simple (so there is a separate rspec-stories gem), then I'd
> be glad to release it sooner.
>
> Thanks for the effort!
>
> Cheers,
> David
>
>
>>
>> Cheers,
>>
>> Chad
>> _______________________________________________
>> rspec-devel mailing list
>> rspec-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-devel
>>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From dchelimsky at gmail.com  Sat Nov  1 16:54:39 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 1 Nov 2008 15:54:39 -0500
Subject: [rspec-devel] Pulling the story runner out of rspec/rspec-rails
In-Reply-To: <16f722280811011350n2cbb7577t38c92f24dbcd7eea@mail.gmail.com>
References: <16f722280810300427l635a5116w1068a85270e3295f@mail.gmail.com>
	<57c63afe0810300656l5c8f185bjb1c6dda9b27b0e61@mail.gmail.com>
	<16f722280811011350n2cbb7577t38c92f24dbcd7eea@mail.gmail.com>
Message-ID: <57c63afe0811011354n3255dda8x7bbd9ad7344e0ac8@mail.gmail.com>

Depend on rspec (as it does now) - that's fine.

On Sat, Nov 1, 2008 at 3:50 PM, Chad Humphries <chad.humphries at gmail.com> wrote:
> My fork of RSpec has the story runner extracted.  I have a question
> about the story runner gem though.   Is is to be more of a stand-alone
> gem ala cucumber, or can it be dependent on RSpec?   I think I have an
> approach working with a dependency on RSpec now.
>
> --
> Chad
>
> On Thu, Oct 30, 2008 at 9:56 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
>> On Thu, Oct 30, 2008 at 6:27 AM, Chad Humphries
>> <chad.humphries at gmail.com> wrote:
>>> Hey again,
>>>
>>> I've been working on my fork of RSpec recently and I have removed
>>> story runner a few different ways.  I can pull it out into it's own
>>> gem fairly quickly, although the gem will require a little more of my
>>> time to make it prim and proper for public consumption.  My question
>>> is this, do you still want the story runner pulled out into a separate
>>> gem?  I'm not interested into maintaining it long-term, but I do have
>>> some time to take care of the extraction and hand off to whomever
>>> would like to.
>>
>> This is definitely in the plan. I wasn't planning to tackle it until
>> later this year, perhaps early '09, but if you can get it working and
>> clean and simple (so there is a separate rspec-stories gem), then I'd
>> be glad to release it sooner.
>>
>> Thanks for the effort!
>>
>> Cheers,
>> David
>>
>>
>>>
>>> Cheers,
>>>
>>> Chad
>>> _______________________________________________
>>> rspec-devel mailing list
>>> rspec-devel at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-devel
>>>
>> _______________________________________________
>> rspec-devel mailing list
>> rspec-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-devel
>>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From jdean at pivotallabs.com  Sun Nov  2 22:51:52 2008
From: jdean at pivotallabs.com (Jeff Dean)
Date: Sun, 2 Nov 2008 22:51:52 -0500
Subject: [rspec-devel] Better inspect method for active record objects in
	rspec-rails
Message-ID: <BCF81DCB-7981-49D7-8950-EB3E3597C1CB@pivotallabs.com>

I'm working on a rails project where we have a complex object graph  
and often find ourselves having to assert on the exact contents of  
arrays of ActiveRecord objects.   Several of our tables have 20+  
fields, so calling @person.inspect generates a very lengthy string.

A recent post suggested mapping/collecting certain fields to shorten  
the error message and make things look prettier.  Since the only thing  
in question here is what the error message looked like, I thought it  
could be useful to have RSpec look for a custom inspect method first  
(say, rspec_inspect), and call it if it's there - defaulting to  
inspect.  So a spec_helper might look like this:

Person.class_eval do
   def rspec_inspect
     "<#{name} (#{id || 'new_record'})>"
   end
end

Then, whenever you call include, the error message would look like:

expected [<Jane (2)>, <Fred (3)>] to include [<Joe (new record)>]

Since the override would happen in a spec helper, we wouldn't have to  
mess with AR's inspect method at all and we wouldn't have to map/ 
collect for good error messages.

As far as making it happen, I would suggest:

Alias rspec_inspect to inspect on object, so everything has it by  
default (we could go with checking if it the object responds_to  
rspec_inspect, which would cleaner but slower as well)
Adding new examples to every matcher spec
Change all calls to inspect in all of the matcher error messages and  
descriptions to call rspec_inspect (and anywhere else that objects are  
inspected)
Writing some developer documentation/wiki page entries to alert future  
developers to the pattern

Mike Grafton also suggested (although somewhat jokingly) that we could  
call it inspec instead of rspec_inspect.  I like that idea a lot.

I'd be willing to put the leg work in to creating a patch if people  
think it would be useful and a likely candidate for inclusion.

Thoughts?

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081102/2fadd946/attachment.html>

From dchelimsky at gmail.com  Mon Nov  3 07:15:40 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 3 Nov 2008 06:15:40 -0600
Subject: [rspec-devel] Better inspect method for active record objects
	in rspec-rails
In-Reply-To: <BCF81DCB-7981-49D7-8950-EB3E3597C1CB@pivotallabs.com>
References: <BCF81DCB-7981-49D7-8950-EB3E3597C1CB@pivotallabs.com>
Message-ID: <57c63afe0811030415x12c26320t3fb59b4d013c2e1f@mail.gmail.com>

On Sun, Nov 2, 2008 at 9:51 PM, Jeff Dean <jdean at pivotallabs.com> wrote:
> I'm working on a rails project where we have a complex object graph and
> often find ourselves having to assert on the exact contents of arrays of
> ActiveRecord objects.   Several of our tables have 20+ fields, so calling
> @person.inspect generates a very lengthy string.
> A recent post suggested mapping/collecting certain fields to shorten the
> error message and make things look prettier.  Since the only thing in
> question here is what the error message looked like, I thought it could be
> useful to have RSpec look for a custom inspect method first (say,
> rspec_inspect), and call it if it's there - defaulting to inspect.  So a
> spec_helper might look like this:
> Person.class_eval do
>   def rspec_inspect
>     "<#{name} (#{id || 'new_record'})>"
>   end
> end
> Then, whenever you call include, the error message would look like:
> expected [<Jane (2)>, <Fred (3)>] to include [<Joe (new record)>]
> Since the override would happen in a spec helper, we wouldn't have to mess
> with AR's inspect method at all and we wouldn't have to map/collect for good
> error messages.
> As far as making it happen, I would suggest:
>
> Alias rspec_inspect to inspect on object, so everything has it by default
> (we could go with checking if it the object responds_to rspec_inspect, which
> would cleaner but slower as well)
> Adding new examples to every matcher spec
> Change all calls to inspect in all of the matcher error messages and
> descriptions to call rspec_inspect (and anywhere else that objects are
> inspected)
> Writing some developer documentation/wiki page entries to alert future
> developers to the pattern
>
> Mike Grafton also suggested (although somewhat jokingly) that we could call
> it inspec instead of rspec_inspect.  I like that idea a lot.
> I'd be willing to put the leg work in to creating a patch if people think it
> would be useful and a likely candidate for inclusion.
> Thoughts?
> Jeff

Hey Jeff,

I'm all for solving this problem, though I have some different ideas
about the approach.

Would you mind posting this request to lighthouse so we can have the
conversation there?

Thanks,
David

From dchelimsky at gmail.com  Fri Nov  7 10:03:41 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 7 Nov 2008 10:03:41 -0500
Subject: [rspec-devel] The RSpec Book
Message-ID: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>

Hey all,

I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
is almost here. The plan is:

* beta/pdf in December, 2008
* print in April, 2009

The RSpec Book, authored by me, Dave Astels, Zach Dennis, Aslak
Helles?y, Bryan Helmkamp, and Dan North, will comprise material on
RSpec, Cucumber, Webrat and other tools, plus material on BDD, TDD,
ATDP, mocks, BDD in Rails, extending RSpec, and more.

You can read more about it at
http://www.pragprog.com/titles/achbd/the-rspec-book.

Cheers,
David

From luislavena at gmail.com  Fri Nov  7 10:23:24 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 7 Nov 2008 12:23:24 -0300
Subject: [rspec-devel] The RSpec Book
In-Reply-To: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
References: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
Message-ID: <71166b3b0811070723i77d77742pd0f25591767025fa@mail.gmail.com>

On Fri, Nov 7, 2008 at 12:03 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> Hey all,
>
> I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
> is almost here. The plan is:
>
> * beta/pdf in December, 2008
> * print in April, 2009
>
> The RSpec Book, authored by me, Dave Astels, Zach Dennis, Aslak
> Helles?y, Bryan Helmkamp, and Dan North, will comprise material on
> RSpec, Cucumber, Webrat and other tools, plus material on BDD, TDD,
> ATDP, mocks, BDD in Rails, extending RSpec, and more.
>
> You can read more about it at
> http://www.pragprog.com/titles/achbd/the-rspec-book.
>

Yay! great news David!

There is no pre-order button!?!?
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From pergesu at gmail.com  Fri Nov  7 10:39:25 2008
From: pergesu at gmail.com (Pat Maddox)
Date: Fri, 07 Nov 2008 07:39:25 -0800
Subject: [rspec-devel] The RSpec Book
In-Reply-To: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
	(David Chelimsky's message of "Fri\, 7 Nov 2008 10\:03\:41 -0500")
References: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
Message-ID: <m2ljvvo89e.fsf@paltswif01.r2.pt.cox.cci>

"David Chelimsky" <dchelimsky at gmail.com> writes:

> Hey all,
>
> I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
> is almost here. The plan is:
>
> * beta/pdf in December, 2008
> * print in April, 2009
>
> The RSpec Book, authored by me, Dave Astels, Zach Dennis, Aslak
> Helles?y, Bryan Helmkamp, and Dan North, will comprise material on
> RSpec, Cucumber, Webrat and other tools, plus material on BDD, TDD,
> ATDP, mocks, BDD in Rails, extending RSpec, and more.
>
> You can read more about it at
> http://www.pragprog.com/titles/achbd/the-rspec-book.

Congrats, man, can't wait!!

Pat

From ben at benmabey.com  Fri Nov  7 10:39:16 2008
From: ben at benmabey.com (Ben Mabey)
Date: Fri, 07 Nov 2008 08:39:16 -0700
Subject: [rspec-devel] The RSpec Book
In-Reply-To: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
References: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
Message-ID: <49146124.7010005@benmabey.com>

David Chelimsky wrote:
> Hey all,
>
> I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
> is almost here. The plan is:
>
> * beta/pdf in December, 2008
> * print in April, 2009
>
> The RSpec Book, authored by me, Dave Astels, Zach Dennis, Aslak
> Helles?y, Bryan Helmkamp, and Dan North, will comprise material on
> RSpec, Cucumber, Webrat and other tools, plus material on BDD, TDD,
> ATDP, mocks, BDD in Rails, extending RSpec, and more.
>
> You can read more about it at
> http://www.pragprog.com/titles/achbd/the-rspec-book.
>
> Cheers,
> David
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>   
Congratulations!  I look forward to reading it.

-Ben

From josephwilk at joesniff.co.uk  Fri Nov  7 13:44:35 2008
From: josephwilk at joesniff.co.uk (Joseph Wilk-2)
Date: Fri, 7 Nov 2008 10:44:35 -0800 (PST)
Subject: [rspec-devel] The RSpec Book
In-Reply-To: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
References: <57c63afe0811070703w7a8320eoa5c259d7d8263c4b@mail.gmail.com>
Message-ID: <20386598.post@talk.nabble.com>


Brilliant news! Thanks for all your hard work on this David + everyone else
who is involved. 

Lots of tasty Cucumber included as well!

Joseph Wilk


David Chelimsky-2 wrote:
> 
> Hey all,
> 
> I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
> is almost here. The plan is:
> 
> * beta/pdf in December, 2008
> * print in April, 2009
> 
> The RSpec Book, authored by me, Dave Astels, Zach Dennis, Aslak
> Helles?y, Bryan Helmkamp, and Dan North, will comprise material on
> RSpec, Cucumber, Webrat and other tools, plus material on BDD, TDD,
> ATDP, mocks, BDD in Rails, extending RSpec, and more.
> 
> You can read more about it at
> http://www.pragprog.com/titles/achbd/the-rspec-book.
> 
> Cheers,
> David
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/The-RSpec-Book-tp20382517p20386598.html
Sent from the rspec-devel mailing list archive at Nabble.com.


From aslak.hellesoy at gmail.com  Tue Nov 11 17:24:56 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 11 Nov 2008 23:24:56 +0100
Subject: [rspec-devel] Cucumber release?
Message-ID: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>

Hi.

I'd like to make a new release. Anything pressing before I do?

Aslak

From caius at caius.name  Tue Nov 11 17:31:15 2008
From: caius at caius.name (Caius Durling)
Date: Tue, 11 Nov 2008 22:31:15 +0000
Subject: [rspec-devel] Cucumber release?
In-Reply-To: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
References: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
Message-ID: <25A854B6-C5CD-40FF-8357-35D6AF0782FE@caius.name>


On 11 Nov 2008, at 22:24, aslak hellesoy wrote:

> I'd like to make a new release. Anything pressing before I do?


Test it thoroughly to stop there being 3 releases in the next week. :)

</half_joking>

C
---
Caius Durling
caius at caius.name
+44 (0) 7960 268 100
http://caius.name/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081111/9b929172/attachment.html>

From aslak.hellesoy at gmail.com  Tue Nov 11 17:43:38 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 11 Nov 2008 23:43:38 +0100
Subject: [rspec-devel] Cucumber release?
In-Reply-To: <25A854B6-C5CD-40FF-8357-35D6AF0782FE@caius.name>
References: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
	<25A854B6-C5CD-40FF-8357-35D6AF0782FE@caius.name>
Message-ID: <8d961d900811111443p132739c7p9d03eee91a251ddd@mail.gmail.com>

On Tue, Nov 11, 2008 at 11:31 PM, Caius Durling <caius at caius.name> wrote:
>
> On 11 Nov 2008, at 22:24, aslak hellesoy wrote:
>
> I'd like to make a new release. Anything pressing before I do?
>
> Test it thoroughly to stop there being 3 releases in the next week. :)

I meant Cucumber, not RSpec.

Sorry David ;-)

> </half_joking>
> C
> ---
> Caius Durling
> caius at caius.name
> +44 (0) 7960 268 100
> http://caius.name/
>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From luislavena at gmail.com  Tue Nov 11 17:54:58 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 11 Nov 2008 19:54:58 -0300
Subject: [rspec-devel] Cucumber release?
In-Reply-To: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
References: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
Message-ID: <71166b3b0811111454n22322b62q1fe2943e70cfea75@mail.gmail.com>

On Tue, Nov 11, 2008 at 7:24 PM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
> Hi.
>
> I'd like to make a new release. Anything pressing before I do?
>

Yep, let me check why the new UTF stuff is eating my 'a' letters and
I'll get back to you :-D

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From dchelimsky at gmail.com  Tue Nov 11 19:35:45 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 11 Nov 2008 18:35:45 -0600
Subject: [rspec-devel] Cucumber release?
In-Reply-To: <8d961d900811111443p132739c7p9d03eee91a251ddd@mail.gmail.com>
References: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
	<25A854B6-C5CD-40FF-8357-35D6AF0782FE@caius.name>
	<8d961d900811111443p132739c7p9d03eee91a251ddd@mail.gmail.com>
Message-ID: <57c63afe0811111635j5fff2548s83f118f366223b64@mail.gmail.com>

On Tue, Nov 11, 2008 at 4:43 PM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
> On Tue, Nov 11, 2008 at 11:31 PM, Caius Durling <caius at caius.name> wrote:
>>
>> On 11 Nov 2008, at 22:24, aslak hellesoy wrote:
>>
>> I'd like to make a new release. Anything pressing before I do?
>>
>> Test it thoroughly to stop there being 3 releases in the next week. :)
>
> I meant Cucumber, not RSpec.

Ouch!

> Sorry David ;-)

Actually - good news from RubyConf - the next release of RubyGems,
which was being hacked on at RC, promises to support letters in
versions. This means we'll be able to do properly labeled release
candidates like rspec-1.2.0.RC1. The way it'll work is that when you
do gem update gemname, it will ignore anything w/ letters in it, but
you can specify that if there is pre-release version greater than the
last release that you want that with a command line flag.

Hooray for improved release support!

Cheers,
David

>
>> </half_joking>
>> C
>> ---
>> Caius Durling
>> caius at caius.name
>> +44 (0) 7960 268 100
>> http://caius.name/
>>
>> _______________________________________________
>> rspec-devel mailing list
>> rspec-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-devel
>>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From josephwilk at joesniff.co.uk  Wed Nov 12 07:43:07 2008
From: josephwilk at joesniff.co.uk (Joseph Wilk-2)
Date: Wed, 12 Nov 2008 04:43:07 -0800 (PST)
Subject: [rspec-devel] Cucumber release?
In-Reply-To: <71166b3b0811111454n22322b62q1fe2943e70cfea75@mail.gmail.com>
References: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
	<71166b3b0811111454n22322b62q1fe2943e70cfea75@mail.gmail.com>
Message-ID: <20459570.post@talk.nabble.com>


Checkout this ticket about the missing 'a's

http://rspec.lighthouseapp.com/projects/16211/tickets/81-windows-all-the-a-characters-in-the-output-have-gone-on-strike#ticket-81-6


Luis Lavena wrote:
> 
> On Tue, Nov 11, 2008 at 7:24 PM, aslak hellesoy
> <aslak.hellesoy at gmail.com> wrote:
>> Hi.
>>
>> I'd like to make a new release. Anything pressing before I do?
>>
> 
> Yep, let me check why the new UTF stuff is eating my 'a' letters and
> I'll get back to you :-D
> 
> -- 
> Luis Lavena
> AREA 17
> -
> Human beings, who are almost unique in having the ability to learn from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/Cucumber-release--tp20449782p20459570.html
Sent from the rspec-devel mailing list archive at Nabble.com.


From luislavena at gmail.com  Wed Nov 12 07:47:59 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 12 Nov 2008 09:47:59 -0300
Subject: [rspec-devel] Cucumber release?
In-Reply-To: <20459570.post@talk.nabble.com>
References: <8d961d900811111424k1ac23ef1ua9ae5f855775663c@mail.gmail.com>
	<71166b3b0811111454n22322b62q1fe2943e70cfea75@mail.gmail.com>
	<20459570.post@talk.nabble.com>
Message-ID: <71166b3b0811120447j7c010768na1dbead4cb0ed1bc@mail.gmail.com>

On Wed, Nov 12, 2008 at 9:43 AM, Joseph Wilk-2
<josephwilk at joesniff.co.uk> wrote:
>
> Checkout this ticket about the missing 'a's
>
> http://rspec.lighthouseapp.com/projects/16211/tickets/81-windows-all-the-a-characters-in-the-output-have-gone-on-strike#ticket-81-6
>

Thank you Joseph.

Didn't had the time last week to check that out by myself. I'll work
out alternatives to win32console on my github fork and get it working,
which I believe is possible.

Regards,
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From aslak.hellesoy at gmail.com  Wed Nov 12 10:53:39 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Wed, 12 Nov 2008 16:53:39 +0100
Subject: [rspec-devel] ANN Cucumber 0.1.9
Message-ID: <8d961d900811120753j131130e5oca9694239653c130@mail.gmail.com>

I'm pleased to announce Cucumber 0.1.9 - full changelog here:
http://github.com/aslakhellesoy/cucumber/tree/v0.1.9/History.txt

gem install cucumber (As usual, the gem will take a few hours to rsync
around the world).

With this release Cucumber supports 19 natural languages! Cucumber is
now represented on all continents. Please send more translations.
(I know that Australians say "Nifty shit" for "Feature", but I don't
know the other words).

Cucumber also has Autotest support now.

It turns out Git+GitHub is working great for this project. There are
50+ forks and 300+ followers and I keep pulling in high quality
improvements several times a week.
I'd especially like to thank Joseph Wilk, who has contributed a ton of
great features and fixes. Joseph is now part of the "official"
Cucumber team.

So what's next? A couple of things. I will focus on improving the
internal structure of features to make it easier to manipulate the
contents of features programmatically.
I'm planning to introduce a better AST. For users of Cucumber this
will not be noticeable, except that support for tables will be much
better. One thing I have in mind is
to be able to push actual values back into a table and open up for
custom interpretation of tables. I also want to make it possible to
customise how table "results" are
displayed (for example comparing actual and expected values inside
individual cells).

When these internal changes start to take shape it's time to slap some
REST around Cucumber so we can integrate it better with authoring
tools. Then we will invite the
customers to the party.

Thanks to everybody who has reported bugs, come with suggestions and
contributed code so far. Enjoy the new release!

Cheers,
Aslak

From joshknowles at gmail.com  Wed Nov 12 16:37:20 2008
From: joshknowles at gmail.com (Josh Knowles)
Date: Wed, 12 Nov 2008 16:37:20 -0500
Subject: [rspec-devel] Thoughts after my initial experience with Cucumber
	Scenario Tables
Message-ID: <c18843c60811121337x6d0e2d95q5c8facc8794d8459@mail.gmail.com>

On Wed, Nov 12, 2008 at 10:53 AM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
> So what's next? A couple of things. I will focus on improving the
> internal structure of features to make it easier to manipulate the
> contents of features programmatically.
> I'm planning to introduce a better AST. For users of Cucumber this
> will not be noticeable, except that support for tables will be much
> better. One thing I have in mind is
> to be able to push actual values back into a table and open up for
> custom interpretation of tables. I also want to make it possible to
> customise how table "results" are
> displayed (for example comparing actual and expected values inside
> individual cells).

I used the table feature for the first time this week, and while I'm
quite happy with the end result I wanted to share some of the
frustrations that I found as it seems like this feature is going to
get some love in the near future.

My pair and I were working on a story which included redirecting a
user if they accessed a restricted URL.  My first pass at the scenario
was written as follows:

  Scenario: Accessing a group as a non-member
      Given a group named Tigers
      And I am not a member of the Tigers
      When I access the media gallery
      Then I should be redirected to the Tigers public page

After getting this scenario to pass we decided that it made sense to
use a Scenario Table to add the rest of the restricted URLs.  My first
attempt at this is as follows:

    Scenario: Accessing a group as a non-member
      Given a group named Tigers
      And I am not a member of the Tigers
      When I access the media gallery
      Then I should be redirected to the Tigers public page

    More Examples:
      | path                |
      | the news page |
      | the roster        |

Unfortunately I didn't read the documentation closely enough, and what
I learned is that Cucumber will use the table values to replace
variables in the order that they are found, which makes sense, but
this causes problems when you have steps above the places holders
which you aren't intending be filled in via examples in the table,
such as Given /a group named (\w+)/.

I ended up re-writing my scenario to use the other style of table,
which I've included below, but by doing so I had to create a
state-variable to hold all of the path's which I then iterated over in
the "Then".

  Scenario: Accessing a group as a non-member

    Given a group named Tigers
    And I am not a member of the Tigers
    When I access the following paths:
      | path                    |
      | the tigers' profile     |
      | the tigers news page    |
      | the tigers gallery page |
      | the tigers' schedule    |
      | the tigers' roster page |
    Then I should be redirected to the Tigers' public page


After digging into the code a bit I don't really have any suggestions
on what could be done differently, but I wanted to start a
conversation around this feature before going off and trying to solve
it.

-- 
Josh Knowles
phone: 509-979-1593
email:  joshknowles at gmail.com
web:    http://joshknowles.com

From dchelimsky at gmail.com  Wed Nov 12 16:41:28 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 12 Nov 2008 15:41:28 -0600
Subject: [rspec-devel] Thoughts after my initial experience with
	Cucumber Scenario Tables
In-Reply-To: <c18843c60811121337x6d0e2d95q5c8facc8794d8459@mail.gmail.com>
References: <c18843c60811121337x6d0e2d95q5c8facc8794d8459@mail.gmail.com>
Message-ID: <57c63afe0811121341t4440a248s128ff522b08dc1cd@mail.gmail.com>

On Wed, Nov 12, 2008 at 3:37 PM, Josh Knowles <joshknowles at gmail.com> wrote:
> On Wed, Nov 12, 2008 at 10:53 AM, aslak hellesoy
> <aslak.hellesoy at gmail.com> wrote:
>> So what's next? A couple of things. I will focus on improving the
>> internal structure of features to make it easier to manipulate the
>> contents of features programmatically.
>> I'm planning to introduce a better AST. For users of Cucumber this
>> will not be noticeable, except that support for tables will be much
>> better. One thing I have in mind is
>> to be able to push actual values back into a table and open up for
>> custom interpretation of tables. I also want to make it possible to
>> customise how table "results" are
>> displayed (for example comparing actual and expected values inside
>> individual cells).
>
> I used the table feature for the first time this week, and while I'm
> quite happy with the end result I wanted to share some of the
> frustrations that I found as it seems like this feature is going to
> get some love in the near future.
>
> My pair and I were working on a story which included redirecting a
> user if they accessed a restricted URL.  My first pass at the scenario
> was written as follows:
>
>  Scenario: Accessing a group as a non-member
>      Given a group named Tigers
>      And I am not a member of the Tigers
>      When I access the media gallery
>      Then I should be redirected to the Tigers public page
>
> After getting this scenario to pass we decided that it made sense to
> use a Scenario Table to add the rest of the restricted URLs.  My first
> attempt at this is as follows:
>
>    Scenario: Accessing a group as a non-member
>      Given a group named Tigers
>      And I am not a member of the Tigers
>      When I access the media gallery
>      Then I should be redirected to the Tigers public page
>
>    More Examples:
>      | path                |
>      | the news page |
>      | the roster        |
>
> Unfortunately I didn't read the documentation closely enough, and what
> I learned is that Cucumber will use the table values to replace
> variables in the order that they are found, which makes sense, but
> this causes problems when you have steps above the places holders
> which you aren't intending be filled in via examples in the table,
> such as Given /a group named (\w+)/.
>
> I ended up re-writing my scenario to use the other style of table,
> which I've included below, but by doing so I had to create a
> state-variable to hold all of the path's which I then iterated over in
> the "Then".
>
>  Scenario: Accessing a group as a non-member
>
>    Given a group named Tigers
>    And I am not a member of the Tigers
>    When I access the following paths:
>      | path                    |
>      | the tigers' profile     |
>      | the tigers news page    |
>      | the tigers gallery page |
>      | the tigers' schedule    |
>      | the tigers' roster page |
>    Then I should be redirected to the Tigers' public page
>
>
> After digging into the code a bit I don't really have any suggestions
> on what could be done differently, but I wanted to start a
> conversation around this feature before going off and trying to solve
> it.

There's a thread you might want to participate in:
http://rspec.lighthouseapp.com/projects/16211/tickets/57

Cheers,
David

>
> --
> Josh Knowles
> phone: 509-979-1593
> email:  joshknowles at gmail.com
> web:    http://joshknowles.com

From joshknowles at gmail.com  Wed Nov 12 17:02:19 2008
From: joshknowles at gmail.com (Josh Knowles)
Date: Wed, 12 Nov 2008 17:02:19 -0500
Subject: [rspec-devel] Thoughts after my initial experience with
	Cucumber Scenario Tables
In-Reply-To: <57c63afe0811121341t4440a248s128ff522b08dc1cd@mail.gmail.com>
References: <c18843c60811121337x6d0e2d95q5c8facc8794d8459@mail.gmail.com>
	<57c63afe0811121341t4440a248s128ff522b08dc1cd@mail.gmail.com>
Message-ID: <c18843c60811121402m43c47660u607b9e7ea393e45a@mail.gmail.com>

On Wed, Nov 12, 2008 at 4:41 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> There's a thread you might want to participate in:
> http://rspec.lighthouseapp.com/projects/16211/tickets/57

Thanks David, looks like this is already being discussed.

-- 
Josh Knowles
phone: 509-979-1593
email:  joshknowles at gmail.com
web:    http://joshknowles.com

From dchelimsky at gmail.com  Wed Nov 12 17:14:23 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 12 Nov 2008 16:14:23 -0600
Subject: [rspec-devel] Thoughts after my initial experience with
	Cucumber Scenario Tables
In-Reply-To: <c18843c60811121402m43c47660u607b9e7ea393e45a@mail.gmail.com>
References: <c18843c60811121337x6d0e2d95q5c8facc8794d8459@mail.gmail.com>
	<57c63afe0811121341t4440a248s128ff522b08dc1cd@mail.gmail.com>
	<c18843c60811121402m43c47660u607b9e7ea393e45a@mail.gmail.com>
Message-ID: <57c63afe0811121414u4de7ae39tb423e13f066eab4@mail.gmail.com>

On Wed, Nov 12, 2008 at 4:02 PM, Josh Knowles <joshknowles at gmail.com> wrote:
> On Wed, Nov 12, 2008 at 4:41 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
>> There's a thread you might want to participate in:
>> http://rspec.lighthouseapp.com/projects/16211/tickets/57
>
> Thanks David, looks like this is already being discussed.

It is, but please share your thoughts there - it'll be good to have
them in context later when we wonder how the hell we landed where we
did :)

>
> --
> Josh Knowles
> phone: 509-979-1593
> email:  joshknowles at gmail.com
> web:    http://joshknowles.com

From dchelimsky at gmail.com  Fri Nov 21 05:34:28 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 21 Nov 2008 04:34:28 -0600
Subject: [rspec-devel] Ruby1.9 and rcov
Message-ID: <57c63afe0811210234q7f79f0f1p2adb5df55a8ed52c@mail.gmail.com>

If anybody is interested, I'd like some feedback on
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/610.

Thank you.

David

From dchelimsky at gmail.com  Fri Nov 21 05:36:19 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 21 Nov 2008 04:36:19 -0600
Subject: [rspec-devel] Ruby1.9 and rcov
In-Reply-To: <57c63afe0811210234q7f79f0f1p2adb5df55a8ed52c@mail.gmail.com>
References: <57c63afe0811210234q7f79f0f1p2adb5df55a8ed52c@mail.gmail.com>
Message-ID: <57c63afe0811210236q1752fc30xbf6c03c76418eba@mail.gmail.com>

On Fri, Nov 21, 2008 at 4:34 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> If anybody is interested, I'd like some feedback on
> http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/610.

Please disregard "and rcov" in the subject.

>
> Thank you.
>
> David
>

From baz at madeofstone.net  Fri Nov 21 13:32:41 2008
From: baz at madeofstone.net (Rahoul Baruah)
Date: Fri, 21 Nov 2008 18:32:41 +0000
Subject: [rspec-devel] Getting started with RSpec and Cucumber
In-Reply-To: <57c63afe0811210234q7f79f0f1p2adb5df55a8ed52c@mail.gmail.com>
References: <57c63afe0811210234q7f79f0f1p2adb5df55a8ed52c@mail.gmail.com>
Message-ID: <AD29A378-B019-4F3C-A949-E65331CB427B@madeofstone.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

A bit of shameless self-promotion - I've done a short presentation on  
how we, at Brightbox, are using RSpec and Cucumber to build our  
internal systems.

Hope some of you find it useful.

http://blog.brightbox.co.uk/posts/using-rspec-cucumber-and-user-stories-to-build-our-internal-systems

Cheers,

Baz.

- --
Brightbox
[serious rails hosting]
http://brightbox.co.uk
- --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEUEARECAAYFAkkm/skACgkQu0BNRvjN8xTHHQCYjhJRwgOQ/5Wbrob6VCSg6J5/
5wCfR2pf8e025ymj8o8H3GWMRh1SXLs=
=H5q1
-----END PGP SIGNATURE-----

From aslak.hellesoy at gmail.com  Fri Nov 28 17:37:20 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 28 Nov 2008 23:37:20 +0100
Subject: [rspec-devel] JS-Kit comments
Message-ID: <8d961d900811281437p5a28368ct23fce56af4db28d@mail.gmail.com>

I just discovered this awesome comments system: http://js-kit.com/

What do you think about adding that to the RSpec website and Cucumber Wiki
pages? Would it be useful to improve quality of docs?

Aslak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081128/b8f3c60f/attachment.html>

From dchelimsky at gmail.com  Fri Nov 28 19:44:41 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 28 Nov 2008 18:44:41 -0600
Subject: [rspec-devel] JS-Kit comments
In-Reply-To: <8d961d900811281437p5a28368ct23fce56af4db28d@mail.gmail.com>
References: <8d961d900811281437p5a28368ct23fce56af4db28d@mail.gmail.com>
Message-ID: <57c63afe0811281644mf2bf75aoc3689b2f8b311376@mail.gmail.com>

On Fri, Nov 28, 2008 at 4:37 PM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
> I just discovered this awesome comments system: http://js-kit.com/
>
> What do you think about adding that to the RSpec website and Cucumber Wiki
> pages? Would it be useful to improve quality of docs?

I'm planning to do a redesign and overall restructuring of the RSpec
website w/ Randy from Articulated Man in late Dec/early January, so I
don't really want to make any big changes to what is there now.

That said, I'll certainly take a look at js-kit before we do anything.

As for the wiki pages, I'm not sure what liberty we have to run js on
github. I know there is talk of supporting some level of this, but I
don't know how much. Wanna check that out w/ the github folken?

>
> Aslak
>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From aslak.hellesoy at gmail.com  Fri Nov 28 19:58:11 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sat, 29 Nov 2008 01:58:11 +0100
Subject: [rspec-devel] JS-Kit comments
In-Reply-To: <57c63afe0811281644mf2bf75aoc3689b2f8b311376@mail.gmail.com>
References: <8d961d900811281437p5a28368ct23fce56af4db28d@mail.gmail.com>
	<57c63afe0811281644mf2bf75aoc3689b2f8b311376@mail.gmail.com>
Message-ID: <8d961d900811281658w593260dj674223b0e9214642@mail.gmail.com>

On Sat, Nov 29, 2008 at 1:44 AM, David Chelimsky <dchelimsky at gmail.com>wrote:

> On Fri, Nov 28, 2008 at 4:37 PM, aslak hellesoy
> <aslak.hellesoy at gmail.com> wrote:
> > I just discovered this awesome comments system: http://js-kit.com/
> >
> > What do you think about adding that to the RSpec website and Cucumber
> Wiki
> > pages? Would it be useful to improve quality of docs?
>
> I'm planning to do a redesign and overall restructuring of the RSpec
> website w/ Randy from Articulated Man in late Dec/early January, so I
> don't really want to make any big changes to what is there now.
>
> That said, I'll certainly take a look at js-kit before we do anything.
>
> As for the wiki pages, I'm not sure what liberty we have to run js on
> github. I know there is talk of supporting some level of this, but I
> don't know how much. Wanna check that out w/ the github folken?
>

That's not necessary - I've already added it on this page just to test it:
http://github.com/aslakhellesoy/cucumber/wikis/a-whole-new-world

(Comment link at the bottom - Edit the page to see the 2 lines of js)

Aslak


>
> >
> > Aslak
> >
> > _______________________________________________
> > rspec-devel mailing list
> > rspec-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-devel
> >
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081129/633f07b5/attachment-0001.html>

From dchelimsky at gmail.com  Sat Nov 29 08:14:36 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 29 Nov 2008 07:14:36 -0600
Subject: [rspec-devel] rcumber - rails plugin for cucumber
Message-ID: <57c63afe0811290514x711482adyae16163dd6d8de7c@mail.gmail.com>

FYI:

http://github.com/jgoodsen/rcumber