aidy lewis
2008-Oct-30 17:02 UTC
[rspec-users] After a step fails, if successive steps have been executed and passed, cucumber reports them as skipped
Hi, I have a Given step that fails: For that Scenario the remaining Given''s, When, and Then''s are reported as being skipped, even though theses steps have been executed. Why I am not submitting this to Lighthouse, is that I believe, this may be intentional design. However, would it not be more indicative to have these steps "pass" for example, if the successive steps have executed and passed? Aidy
David Chelimsky
2008-Oct-30 17:07 UTC
[rspec-users] After a step fails, if successive steps have been executed and passed, cucumber reports them as skipped
On Thu, Oct 30, 2008 at 12:02 PM, aidy lewis <aidy.lewis at googlemail.com> wrote:> Hi, > > I have a Given step that fails: For that Scenario the remaining > Given''s, When, and Then''s are reported as being skipped, even though > theses steps have been executed. > > Why I am not submitting this to Lighthouse, is that I believe, this > may be intentional design. > > However, would it not be more indicative to have these steps "pass" > for example, if the successive steps have executed and passed?This is absolutely by design. If a step passes or fails after another has failed, you have no way of knowing if it would still pass or fail once the other one is passing. Cucumber reports the first problem in a scenario so you can fix that one and move on. Cheers, David> > Aidy > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
Stephen Eley
2008-Oct-30 19:18 UTC
[rspec-users] After a step fails, if successive steps have been executed and passed, cucumber reports them as skipped
On Thu, Oct 30, 2008 at 12:07 PM, David Chelimsky <dchelimsky at gmail.com> wrote:> > This is absolutely by design. If a step passes or fails after another > has failed, you have no way of knowing if it would still pass or fail > once the other one is passing. Cucumber reports the first problem in a > scenario so you can fix that one and move on.I''m curious: what''s the logic behind it not just stopping there? -- Have Fun, Steve Eley (sfeley at gmail.com) ESCAPE POD - The Science Fiction Podcast Magazine http://www.escapepod.org
David Chelimsky
2008-Oct-30 19:32 UTC
[rspec-users] After a step fails, if successive steps have been executed and passed, cucumber reports them as skipped
On Thu, Oct 30, 2008 at 2:18 PM, Stephen Eley <sfeley at gmail.com> wrote:> On Thu, Oct 30, 2008 at 12:07 PM, David Chelimsky <dchelimsky at gmail.com> wrote: >> >> This is absolutely by design. If a step passes or fails after another >> has failed, you have no way of knowing if it would still pass or fail >> once the other one is passing. Cucumber reports the first problem in a >> scenario so you can fix that one and move on. > > I''m curious: what''s the logic behind it not just stopping there?Pending steps (post failure) are still reported as pending, so it gives you a sense of where you are in process. Make sense?> > > -- > Have Fun, > Steve Eley (sfeley at gmail.com) > ESCAPE POD - The Science Fiction Podcast Magazine > http://www.escapepod.org > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >