You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a story fails because a step throws a not implemented exception it would be nice if this translated to an ignored result in the test framework the story is running in. It currently causes the whole test to fail and also prevents any further steps from being run. If a step fails for a different reason it does not prevent other steps from being run and we can see the result of those steps.
Is there a specific reason it was done this way? I have seen the IgnoreStepAttribute but that doesn't appear to work for the fluent api. The above approach worked really well in StoryQ which is why I am suggesting it. I understand the project is not currently being maintained but if there is an agreement on the above then I could put together a PR.
The text was updated successfully, but these errors were encountered:
Hi Matt. I don't use the Fluent Api myself, but happy to help you try to get this PR added. I agree that having a not implemented exception translate into an ignored result in the test framework is the desired behaviour.
Context: Fluent Api
If a story fails because a step throws a not implemented exception it would be nice if this translated to an ignored result in the test framework the story is running in. It currently causes the whole test to fail and also prevents any further steps from being run. If a step fails for a different reason it does not prevent other steps from being run and we can see the result of those steps.
Is there a specific reason it was done this way? I have seen the
IgnoreStepAttribute
but that doesn't appear to work for the fluent api. The above approach worked really well in StoryQ which is why I am suggesting it. I understand the project is not currently being maintained but if there is an agreement on the above then I could put together a PR.The text was updated successfully, but these errors were encountered: