Scenarios operate like the failsafe plugin not sure fire. They are intended to be completely separate, however there is no real reason we couldn't introduce a semantic that supported it. Do you have a suggestion?
Hello Dear Users, Can you help me a little bit with easyb and thucydides? I will be very glad for you.For example, I have 1 story file and there are 3 scenarios:1 scenario:scenario "Admin should has opportunity to create new users". {}2 scenario:scenario "Admin should has opportunity to edit created users". {}and 3 scenario:scenario "Admin should has opportunity to delete users". {}and here is my question, for example if my first scenario will be failed, then how not to run other two scenaries? As a variant, I could make the first scenario - before statment:before "Admin should has opportunity to create new users". {}
but then I got compilation errors...Maybe there is some way to make dependence between scenarios, like in unit tests?Hope for your help:)Thank you, Igor--
You received this message because you are subscribed to the Google Groups "Easyb Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/easyb-users/-/ou1LvbWAPDMJ.
To post to this group, send email to easyb...@googlegroups.com.
To unsubscribe from this group, send email to easyb-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/easyb-users?hl=en.