As the author of the original scenario runner, if Aslak has come up with a
nicer implementation - both in terms of design and hackability - then I say
chuck my one out and use his :)
As long as it is an easy adjustment (i.e. transparent or with an easy
migration) for users of the current scenario
On Thu, Aug 21, 2008 at 6:08 PM, Joseph Wilk <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've been looking through the cucumber documentation and have a couple
> of questions.
>
Hi, Sorry for the late reply,
> I'm curious which of the disadvantages you list would be impossible/very
> difficult in the
Hello,
I've been looking through the cucumber documentation and have a couple
of questions.
I'm curious which of the disadvantages you list would be impossible/very
difficult in the classic story runner. I'm just trying to envisage if
Cucumber and the classic story runner where to co-exist wha
On Wed, Aug 20, 2008 at 6:24 PM, Ben Mabey <[EMAIL PROTECTED]> wrote:
> aslak hellesoy wrote:
>> The RSpec Story runner is likely to be deprecated in favour of the new
>> feature runner (temporarily called Cucumber).
>> http://www.nabble.com/-ANN--Cucumber-td18876816.html
>>
>> The RSpec Story runn
aslak hellesoy wrote:
Of how you would use it. Assume that you have something like this for
scenario-level before/after:
class MySteps < Cucumber::Steps # Same as Story runnner steps_for(:my)
Before do
# This block will run before all scenarios that use steps from MySteps
# Any scenarios
I agree with Pat also. But I think importantly we need a little
tool/guide on converting the old stories to cucumber before any
movement.
I'm currently evaluating moving our stories to cucumber. I'll see if I
can put something together that might help others (if its not already
available?).
A
aslak hellesoy wrote:
> The RSpec Story runner is likely to be deprecated in favour of the new
> feature runner (temporarily called Cucumber).
> http://www.nabble.com/-ANN--Cucumber-td18876816.html
>
> The RSpec Story runner will continue to exist for a while, I just
> wanted to let you know that f
On Wed, Aug 20, 2008 at 5:32 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 20, 2008 at 7:49 AM, aslak hellesoy <[EMAIL PROTECTED]>
> wrote:
>>
>> Regarding Cucumber - yes, the name is completely meaningless, but a
>> couple of chicks who attended my presentation about it at Agile 2008
>>
On Wed, Aug 20, 2008 at 7:49 AM, aslak hellesoy <[EMAIL PROTECTED]>wrote:
>
> Regarding Cucumber - yes, the name is completely meaningless, but a
> couple of chicks who attended my presentation about it at Agile 2008
> told me afterwards it made their mind drift... That's good enough for
> me.
>
On Wed, Aug 20, 2008 at 4:20 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 20, 2008 at 9:04 AM, Jonathan Linowes
> <[EMAIL PROTECTED]> wrote:
>>
>> On Aug 20, 2008, at 2:20 AM, Aslak Hellesøy wrote:
>>
>>> (In Cucumber it's Feature, not Story)
>>
>> no offense, but while you're bein
On Wed, Aug 20, 2008 at 9:04 AM, Jonathan Linowes
<[EMAIL PROTECTED]> wrote:
>
> On Aug 20, 2008, at 2:20 AM, Aslak Hellesøy wrote:
>
>> (In Cucumber it's Feature, not Story)
>
> no offense, but while you're being picky about names, I dont see too much
> difference between 'story' and 'feature'
I
On Aug 20, 2008, at 2:20 AM, Aslak Hellesøy wrote:
(In Cucumber it's Feature, not Story)
no offense, but while you're being picky about names, I dont see too
much difference between 'story' and 'feature'
but 'cucumber' is a really random meaningless name
_
On Wed, Aug 20, 2008 at 8:32 AM, Jim Morris <[EMAIL PROTECTED]> wrote:
> Aslak Hellesøy wrote:
>
>>>
>>> I'd like to have a before story and after story as well as a before
>>> scenario and after scenario.
>>>
>>> Right now I do global setup for a story, and cleanup when the story is
>>> done. I al
On Aug 20, 2008, at 7:04 AM, Jim Morris wrote:
Aslak Hellesøy wrote:
Right now the scope of Before/After is global - i.e. all Before and
After blocks will run before and after each scenario. I have
deliberately postponed adding scoping of this until I better
understand how people want to
On Aug 20, 2008, at 1:04 AM, Pat Maddox wrote:
What do you think is the best thing to do?
I would prefer to merge it into RSpec whenever it's ready. One of the
strong points about RSpec is that it's a complete BDD toolkit: example
framework for developer testing, feature runner for customer
Aslak Hellesøy wrote:
Right now the scope of Before/After is global - i.e. all Before and
After blocks will run before and after each scenario. I have
deliberately postponed adding scoping of this until I better understand
how people want to define this scoping.
Here is one ideas:
class M
On 8/19/08, Pat Maddox <[EMAIL PROTECTED]> wrote:
> I would prefer to merge it into RSpec whenever it's ready.
For whatever its worth I agree with Pat. Most of the short-comings of
the existing story runner that Aslak describes in the Cucumber README
are things that we at weplay have had to hack
> What do you think is the best thing to do?
I would prefer to merge it into RSpec whenever it's ready. One of the
strong points about RSpec is that it's a complete BDD toolkit: example
framework for developer testing, feature runner for customer test, and
the mock objects framework. People can
On Aug 19, 2008, at 6:28 AM, Jim Morris wrote:
aslak hellesoy wrote:
I'm inviting you to provide some constructive feedback about how we
could improve it to make the transition easier for people like
yourself.
I'll give it a try, I'll port some of my stories to cucumber and see
how it goe
aslak hellesoy wrote:
I'm inviting you to provide some constructive feedback about how we
could improve it to make the transition easier for people like
yourself.
I'll give it a try, I'll port some of my stories to cucumber and see how it
goes.
A natural part of software evolution is that
On Mon, Aug 18, 2008 at 9:46 PM, Jim Morris <[EMAIL PROTECTED]> wrote:
> aslak hellesoy wrote:
>
>>
>> The RSpec Story runner is likely to be deprecated in favour of the new
>> feature runner (temporarily called Cucumber).
>> http://www.nabble.com/-ANN--Cucumber-td18876816.html
>
> This is REALLY b
On Mon, Aug 18, 2008 at 2:46 PM, Jim Morris <[EMAIL PROTECTED]> wrote:
> aslak hellesoy wrote:
>
>>
>> The RSpec Story runner is likely to be deprecated in favour of the new
>> feature runner (temporarily called Cucumber).
>> http://www.nabble.com/-ANN--Cucumber-td18876816.html
>
> This is REALLY b
aslak hellesoy wrote:
The RSpec Story runner is likely to be deprecated in favour of the new
feature runner (temporarily called Cucumber).
http://www.nabble.com/-ANN--Cucumber-td18876816.html
This is REALLY bad news!! I asked this question a while back, I have a LOT of code using story
runne
On Aug 18, 2008, at 8:57 PM, aidy lewis wrote:
Hi,
Bret Pettichord tells me yourself and him worked together on an
improvement to the watir example. Could you commit it and i will
expand on it and wrap it up into an AUT object model.
Aidy.
Hi Aidy. So you and I have the same Bret number eh?
Hi,
Bret Pettichord tells me yourself and him worked together on an
improvement to the watir example. Could you commit it and i will
expand on it and wrap it up into an AUT object model.
Aidy.
On 8/18/08, aslak hellesoy <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 3:31 PM, aidy lewis <[EMA
On Mon, Aug 18, 2008 at 3:31 PM, aidy lewis <[EMAIL PROTECTED]> wrote:
> Aslak
>
> 2008/8/18 aslak hellesoy <[EMAIL PROTECTED]>:
>
>>
>> What do you mean by expand?
>>
>> Aslak
>>
>
> I was going to give a more detailed example...
>
That would be awesome. If you're familiar with Git you can clone
Aslak
2008/8/18 aslak hellesoy <[EMAIL PROTECTED]>:
>
> What do you mean by expand?
>
> Aslak
>
I was going to give a more detailed example...
Aidy
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-user
On Mon, Aug 18, 2008 at 3:02 PM, aidy lewis <[EMAIL PROTECTED]> wrote:
> Aslak
>
>> Look in the examples/watir directory:
>> http://github.com/aslakhellesoy/cucumber/tree/master/examples/watir
>>
>> Aslak
>>
> OK. Can I expand on this for your example?
>
What do you mean by expand?
Aslak
> Aidy
Aslak
> Look in the examples/watir directory:
> http://github.com/aslakhellesoy/cucumber/tree/master/examples/watir
>
> Aslak
>
OK. Can I expand on this for your example?
Aidy
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/m
On Mon, Aug 18, 2008 at 2:29 PM, aidy lewis <[EMAIL PROTECTED]> wrote:
> Hi Aslak
>
>
> 2008/8/18 aslak hellesoy <[EMAIL PROTECTED]>:
>> * How to use with Watir
>
> gem sources --add http://gems.github.com/
> gem install aslakhellesoy-cucumber
>
> I am unable top find the Watir and Cucumber example
Hi Aslak
2008/8/18 aslak hellesoy <[EMAIL PROTECTED]>:
> * How to use with Watir
gem sources --add http://gems.github.com/
gem install aslakhellesoy-cucumber
I am unable top find the Watir and Cucumber example
Aidy
___
rspec-users mailing list
rspec-
On Mon, Aug 18, 2008 at 1:24 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> I think it's better to make them separate. Conceptually, the story runner
> slightly confuses the identity of what RSpec is - is it for specifying
> behaviour of individual classes (a la TDD) or is it for specifying the
> beha
I think it's better to make them separate. Conceptually, the story
runner slightly confuses the identity of what RSpec is - is it for
specifying behaviour of individual classes (a la TDD) or is it for
specifying the behaviour of the whole system? I think the describe /
it / should thing is
On Mon, Aug 18, 2008 at 1:06 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
>>
>> The RSpec Story runner is likely to be deprecated in favour of the new
>> feature runner (temporarily called Cucumber).
>> http://www.nabble.com/-ANN--Cucumber-td18876816.html
>>
>
> And this is going to be distributed as
The RSpec Story runner is likely to be deprecated in favour of the new
feature runner (temporarily called Cucumber).
http://www.nabble.com/-ANN--Cucumber-td18876816.html
And this is going to be distributed as a separate plug-in from RSpec?
___
rspec-
On Tue, Aug 12, 2008 at 6:45 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> Can I help the project by writing some docs about the plain-text story
> runner for the rspec.info website? It would surely help me to get it wired
> in my own mind if I have to write it up for the world.
> Would this be helpf
Hello,
I left out of my Rspec story post Selenium/Webrat integration. I thought
I would release that as a separate post.
While I can write about how I deal with Selenium/Webrat in Rspec I'm yet
to use Watir. So I think putting something together on Watir integration
as Matt suggested would be rea
That would be cool, though I think it might be hard to compete with
something like this:
http://www.joesniff.co.uk/ruby/telling-a-good-story-rspec-stories-
from-the-trenches.html
cheers,
Matt
http://blog.mattwynne.net
On 18 Aug 2008, at 08:34, aidy lewis wrote:
Matt,
Do you want to p
Matt,
Do you want to pair on this? I am writing some stuff for the Watir
site. I sent you some example code as well.
Aidy
On 12/08/2008, Matt Wynne <[EMAIL PROTECTED]> wrote:
>
> Can I help the project by writing some docs about the plain-text story
> runner for the rspec.info website? It would
Can I help the project by writing some docs about the plain-text
story runner for the rspec.info website? It would surely help me to
get it wired in my own mind if I have to write it up for the world.
Would this be helpful / appreciated?
What format would you want them in?
cheers,
Matt
___
40 matches
Mail list logo
