We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Incorrect example with defer. Require my stops test execution when a test result fails, and defer stack will not fill.
To Reproduce Steps to reproduce the behavior: look through example: https://github.com/ozontech/allure-go/blob/master/examples/suite_demo/setup_test.go#L92
Expected behavior defer should executed right after context declaration
The text was updated successfully, but these errors were encountered:
what is a main idea of this MR?
Sorry, something went wrong.
The main idea is fix documentation to avoid confusion of newcomers. They may start using defer after t.Require
In common case it make sense but in that example the reason why defer stay there is to highlight semantic of WithTearDown function
It looks like common sense to me that you need to put it in the begging of Test
Let me think day or two about that
fixed in #78
KolesnikDmitriy
No branches or pull requests
Describe the bug
Incorrect example with defer. Require my stops test execution when a test result fails, and defer stack will not fill.
To Reproduce
Steps to reproduce the behavior:
look through example:
https://github.com/ozontech/allure-go/blob/master/examples/suite_demo/setup_test.go#L92
Expected behavior
defer should executed right after context declaration
The text was updated successfully, but these errors were encountered: