For the simple login case, as a quick fix, u can: 1. just stick with aslakhellesoy-cucumber, and
2. create a MERB_ROOT/cucumber.yml using the content from http://github.com/aslakhellesoy/cucumber/tree/master/cucumber.yml Should work ok with the standard setup by merb_cucumber. I've a non-standard setup, have yet to find a solution for it :[ TY == On Fri, Dec 19, 2008 at 1:27 PM, Tze Yang Ng <[email protected]> wrote: > Hmm .. interesting, i'm using 0.1.13, pulled from github a few days > ago and has been working ok. And i just tried: > > 1. aslakhellesoy-cucumber gem, and got the same error as urs > 2. the latest github pull, and got the same erorr as urs > > The 0.1.13 that works a few days ago obviously failed to work now. And > i'm not able to checkout v0.1.13 since there isn't such a branch in > the git. > > Is it possible to do a date-specific git-checkout ? > > TY > > == > > On Fri, Dec 19, 2008 at 2:30 AM, Jon Hancock <[email protected]> wrote: >> >> Just tried with the latest cucumber by installing as: >> sudo gem install aslakhellesoy-cucumber >> (first I uninstalled the other cucumber gem and afterwards, I re-ran >> "merb-gen cucumber --session-type webrat"). >> >> This time the errors are worse: >>> rake features >> (in /Users/jhancock/src/ssmerb) >> Loading init file from /Users/jhancock/src/ssmerb/config/init.rb >> Loading /Users/jhancock/src/ssmerb/config/environments/development.rb >> /Users/jhancock/src/ssmerb/bin/cucumber:15:in `execute': wrong number >> of arguments (0 for 1) (ArgumentError) >> from /Users/jhancock/src/ssmerb/bin/cucumber:15 >> rake aborted! >> Command failed with status (1): [/System/Library/Frameworks/ >> Ruby.framework/...] >> >> (See full trace by running task with --trace) >> >> I must be using the wrong repos or have something messed up if this >> Scenario Outline is working. >> >> thanks, Jon >> >> On Dec 19, 2:17 am, Jon Hancock <[email protected]> wrote: >>> 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 >> >> >> > > > > -- > http://ngty77.blogspot.com > -- 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 -~----------~----~----~----~------~----~------~--~---
