Using `rake cucumber` halts the test once one of the steps fail. To get past this you can use cucumber directly rather than running it using rake. To do this you specify the directory where all the features live. This will run all the scenarios regardless of a failure.
`cucumber portal/src/features` does the trick. I just tested `rake cucumber` with the authentication feature fixed, and it does all the scenarios. Thanks Martyn ----- Original Message ----- From: "Scott Seago" <[email protected]> To: [email protected] Cc: [email protected] Sent: Wednesday, April 21, 2010 7:55:48 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [deltacloud-devel] [PATCH 2/2] Created Pool Cucumber Feature and Step Definitions [email protected] wrote: > From: mtaylor <[email protected]> > > --- > src/features/pool.feature | 63 > +++++++++++++++++++++++++++ > src/features/step_definitions/pool_steps.rb | 50 +++++++++++++++++++++ > src/features/support/env.rb | 8 +++ > src/features/support/paths.rb | 11 +++++ > src/spec/factories/cloud_account.rb | 5 ++ > src/spec/factories/hardware_profile.rb | 7 +++ > src/spec/factories/image.rb | 6 +++ > src/spec/factories/provider.rb | 4 +- > src/spec/factories/realm.rb | 1 + > 9 files changed, 154 insertions(+), 1 deletions(-) > create mode 100644 src/features/pool.feature > create mode 100644 src/features/step_definitions/pool_steps.rb > create mode 100644 src/spec/factories/cloud_account.rb > create mode 100644 src/spec/factories/image.rb > ACK (and to the prior patch too), it all works for me when I run this feature directly. When I just run 'rake cucumber' it doesn't run the new tests though -- is this a problem with setup, or does 'rake cucumber' stop after a prior failed feature? Scott _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
