-
-
Notifications
You must be signed in to change notification settings - Fork 3k
docs: clarify capture fixture precedence over -s #14053
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
Conversation
|
The docs build failure appears to be unrelated to this change. |
|
@Zac-HD Could you please check if that what you had in mind for the issue? |
Zac-HD
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great - thanks for the PR, @Bubble-Interface!
(the CI failure looks unrelated to me)
|
The CI failure is being addressed in #14067. |
0ba948a to
bb28508
Compare
nicoddemus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Backport to 9.0.x: 💚 backport PR created✅ Backport PR branch: Backported as #14073 🤖 @patchback |
Clarify in the capturing tutorial that using capture fixtures such as capsys or capfd re-enables capturing for the duration of the test, even when global capturing is disabled via `-s` or `--capture=no`. Closes #13731 (cherry picked from commit 8f5b07d) Co-authored-by: Bubble-Interface <[email protected]>
closes #13731
Clarify in the capturing tutorial that using capture fixtures such as
capsysorcapfdre-enables capturing for the duration of the test, even when global capturing is disabled via-sor--capture=no.