exactly what I need!!
I just tried your example and am getting a parse error.  I assume my
gems don't have this feature yet.

I am using:
cucumber (0.1.12)
david-merb_cucumber (0.4.1)

Do I need to build a gem from the latest cucumber?  If so, which git
repo is the main one?  I see several forks.

thanks, Jon


On Dec 18, 10:52 pm, "Tze Yang Ng" <[email protected]> wrote:
> U can try the newer feature 'Scenario Outline', i've pasted a gist 
> athttp://gist.github.com/37518.
>
> TY
>
> ==
>
>
>
> On Thu, Dec 18, 2008 at 10:42 PM, Jon Hancock <[email protected]> wrote:
>
> > There's probably a better title for this post, but I'll try to
> > explain.
> > I'm learning cucumber and have a successful default Login "Failed
> > Login" scenario, which is:
>
> > Feature: Login
> >  To ensure the safety of the application
> >  A regular user of the system
> >  Must authenticate before using the app
>
> >  Scenario: Failed Login
> >    Given I am not authenticated
> >    When I go to /login
> >    And I fill in "email" with "i_dont_exist"
> >    And I fill in "password" with "and_i_dont_have_a_password"
> >    And I press "Log In"
> >    Then the login request should fail
> >    Then I should see an error message
>
> > What I want to do with this is have it run itself multiple times for
> > each of a est of failed inputs.  So I have a cucumber table such as:
> > | email | password |
> > | not_an_address | nil |
> > | n...@not | 123455 |
> > | [email protected] | wrong_paasword |
>
> > I've been reading the cucmber tutorials and haven't seen an example
> > for this type of repeated input scenario.
>
> > Any pointers?
>
> > thanks, Jon
>
> --http://ngty77.blogspot.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to