I'd like to do this:
Feature: user signup
Before:
Given I have a cleaned up database
Scenario Outline: Sign Up
Given I am on the signup page
When I sign up using <userid>
Then I should see <message>
Examples:
|userid |message |
|userX |successful signup |
|userX |duplicate userid |
"I have a cleaned up database" runs before every example, making the
second example ('duplicate userid') fail.
On Apr 28, 9:38 am, aslak hellesoy <aslak.helle...@gmail.com> wrote:
> On Tue, Apr 28, 2009 at 6:15 PM, Arco <akl...@gmail.com> wrote:
> > OK - I found a workaround. I simply tag the first scenario with
> > '@first', then
> > do Before('@first') and i get what I want - executing a block once for
> > the feature file.
>
> > Except for one problem: most of my scenarios are done as scenario
> > outlines, which
> > are run multiple times - once for each row of my Example table.
>
> > A workaround to that problem might be to put a 'dummy' scenario that
> > is run before the other scenarios in my feature file...
>
> > �...@first
> > Scenario: Call a before block before running other scenarios...
>
> > But this puts junk in my feature files. Is there a better, cleaner
> > way??
>
> a) Why do you need one thing to happen before a feature?
> b) Why can't you do it before each scenario?
>
> Aslak
>
>
>
> > On Apr 28, 8:32 am, Arco <akl...@gmail.com> wrote:
> > > I also would like a hook that executes a block once before running a
> > > feature file.
>
> > > In my testing i found that:
> > > - Background: executes before each scenario
> > > - Before executes before each scenario
> > > - Before('@tag') executes before each scenario
>
> > > Is there a way to execute a block once before each feature, but not
> > > before each scenario?
>
> > > On Apr 28, 7:08 am, aslak hellesoy <aslak.helle...@gmail.com> wrote:
>
> > > > > Hi -- is it possible to set before and after blocks for individual
> > feature
> > > > > files?
>
> > > > Yes. Use tagged hooks:
> >http://wiki.github.com/aslakhellesoy/cucumber/hooks
>
> > > > Aslak
>
> > > > > I've tried putting them in step files, but they just get called
> > before
> > > > > everything, like they'd been declared in env.rb, which is consistent
> > with
> > > > > how I thought cucumber worked, but I thought I'd best try it anyway.
> > > > > Anyway, I have some features that require a specific state be set up
> > before
> > > > > they run -- is this possible to do, and how would I go about doing
> > it?
> > > > > Thanks for any & all help,
> > > > > Doug.
>
> > > > > _______________________________________________
> > > > > rspec-users mailing list
> > > > > rspec-us...@rubyforge.org
> > > > >http://rubyforge.org/mailman/listinfo/rspec-users
>
> > > > _______________________________________________
> > > > rspec-users mailing list
> > > > rspec-us...@rubyforge.orghttp://
> > rubyforge.org/mailman/listinfo/rspec-users
>
> > > _______________________________________________
> > > rspec-users mailing list
> > > rspec-us...@rubyforge.orghttp://
> > rubyforge.org/mailman/listinfo/rspec-users
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us...@rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-us...@rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
