Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow statements to fail without failure #43

Closed
ThinkingEngine-net opened this issue Sep 5, 2020 · 1 comment
Closed

Allow statements to fail without failure #43

ThinkingEngine-net opened this issue Sep 5, 2020 · 1 comment
Labels
enhancement New feature or request Gherkin Test Execution
Milestone
Release 1.15.0.0

Comments

@ThinkingEngine-net
Copy link
Owner

As a tester, on occasion- because of application behaviour - validation will fail after a command because the pages had been changed. A capability is needed to say it is OK for a statement to fail (e.g. execute without consequence).

There are three possible outcomes:

  • Failure of the step is a failure (current/normal behaviour)
  • Failure is ignored and treated as a pass.
  • Failure is ignored and treated as a warning/issue.

In all cases, the failure will be debugged in test output.
@ThinkingEngine-net ThinkingEngine-net added this to the Release 1.15.0.0 milestone Sep 5, 2020
@ThinkingEngine-net
Copy link
Owner Author

Implemented. Add the following test to the end of any statement:

  • (pass if fail)
  • (warn if fail)

image

Documetation Updated: https://te-wiki.marescal.co.uk/doku.php?id=wiki:pickle:supported_statements#override_failures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Gherkin Test Execution
Projects
None yet
Milestone
Release 1.15.0.0
Development

No branches or pull requests
1 participant
@ThinkingEngine-net