On Jul 4, 2008, at 10:54 PM, Mikel Lindsaar wrote:
On Sat, Jul 5, 2008 at 12:18 PM, Steve Eley <[EMAIL PROTECTED]>
wrote:
On Fri, Jul 4, 2008 at 4:45 PM, David Chelimsky
<[EMAIL PROTECTED]> wrote:
So - how bad do you think this would suck to remove that feature?
Are you
using it yourself?
On Sat, Jul 5, 2008 at 12:18 PM, Steve Eley <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 4, 2008 at 4:45 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>> So - how bad do you think this would suck to remove that feature? Are you
>> using it yourself?
> I'm not, but would it be impractical to extract it
David Chelimsky wrote:
Hey all,
I'm looking for ways to optimize rspec and came upon something
interesting. If I remove handling for auto-generated descriptions (the
thing that allows you to say "specify { 5.should == 5 }" with no
description string) we get an average 35% performance increase
Zach Dennis wrote:
A short experience report regarding this thread:
Early on when stories were introduced to rspec's code base I started
using them, and I tried some different techniques to see what the
sweet spot was for using stories in actual development. To do some of
this I made modifica
On Fri, Jul 4, 2008 at 4:45 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> So - how bad do you think this would suck to remove that feature? Are you
> using it yourself?
I'm not, but would it be impractical to extract it out into some sort
of module or helper and tell people to include it in t
On Fri, Jul 4, 2008 at 4:45 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> So - how bad do you think this would suck to remove that feature? Are you
> using it yourself?
Personally, I *love* this feature, and would not like to see it go.
One of my heuristics for a good spec is that it either a)
On Jul 4, 2008, at 4:45 PM, David Chelimsky wrote:
So - how bad do you think this would suck to remove that feature?
Are you using it yourself?
All thoughts welcome.
Wasn't even aware that feature existed!
___
rspec-users mailing list
rspec-users
On Fri, Jul 4, 2008 at 1:45 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> I'm looking for ways to optimize rspec and came upon something interesting.
> If I remove handling for auto-generated descriptions (the thing that allows
> you to say "specify { 5.should == 5 }" with no descri
On Jul 4, 2008, at 6:29 AM, Olivier Dupuis wrote:
Hello,
Anyone knows of open source projects that uses RSpec and RSpec
Stories? I'd love to see how it is being used in different projects.
There are lots of projects:
rspec itself,
rubinius / rubyspec
a series of rails plugins, like:
Hey all,
I'm looking for ways to optimize rspec and came upon something
interesting. If I remove handling for auto-generated descriptions (the
thing that allows you to say "specify { 5.should == 5 }" with no
description string) we get an average 35% performance increase per
expectation. 3
Strac uses rspec examples and stories.
http://github.com/mvanholstyn/strac
Zach
On Fri, Jul 4, 2008 at 11:23 AM, David Chelimsky <[EMAIL PROTECTED]>
wrote:
> On Jul 4, 2008, at 5:29 AM, Olivier Dupuis wrote:
>
> Hello,
>>
>> Anyone knows of open source projects that uses RSpec and RSpec Storie
A short experience report regarding this thread:
Early on when stories were introduced to rspec's code base I started using
them, and I tried some different techniques to see what the sweet spot was
for using stories in actual development. To do some of this I made
modifications to rspec (this was
On Fri, Jul 4, 2008 at 6:28 AM, David Chelimsky <[EMAIL PROTECTED]>
wrote:
> On Jul 3, 2008, at 10:55 PM, Mark Wilden wrote:
>
> The problem I just found with shared specs is that if one fails, you don't
>> see the sharer in the callstack, so you really don't know what went wrong.
>>
>
> Even if
On Jul 4, 2008, at 5:29 AM, Olivier Dupuis wrote:
Hello,
Anyone knows of open source projects that uses RSpec and RSpec
Stories? I'd love to see how it is being used in different projects.
Here are a few that I know of:
rspec examples (no stories)
* http://github.com/wycats/merb-core and
I know there are stories in the restful-authentication plugin
http://github.com/technoweenie/restful-authentication/tree/master/generators/authenticated/templates/stories
Erin
On 4 Jul 2008, at 11:29, Olivier Dupuis wrote:
Hello,
Anyone knows of open source projects that uses RSpec and RSpe
Someone on the list was just referencing Typo -
http://svn.typosphere.org/typo/trunk/spec/controllers/comments_controller_spec.rb
Doesn't look like they use stories, though.
On 4-Jul-08, at 4:29 AM, Olivier Dupuis wrote:
Hello,
Anyone knows of open source projects that uses RSpec and RSpec
On Jul 3, 2008, at 10:55 PM, Mark Wilden wrote:
The problem I just found with shared specs is that if one fails, you
don't see the sharer in the callstack, so you really don't know what
went wrong.
Even if you run it with --backtrace?
///ark
Hello,
Anyone knows of open source projects that uses RSpec and RSpec Stories? I'd
love to see how it is being used in different projects.
Thank you
Olivier Dupuis
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/lis
> Unless you're looking for the steps to show up when you run things, why not
> just have a helper method that does the setup for you and then have a Given
> step that invokes that method?
>
> I know I can extract logic into steps, but I'd like the pre-requisite
>> scenarios to have some assertion
Ben Mabey wrote:
Gregg Pollack wrote:
You know how sometimes you look in /log/test.log for debug information
like which test caused a certain render or query?
I found this post which shows how to get test information printed out in
your test.log with test:unit and shoulda, but I'm not sure ther
20 matches
Mail list logo
