-
Notifications
You must be signed in to change notification settings - Fork 144
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
Warnings #185
Comments
There's ample talk about whether JUnit reporting structure (the XML schema) supports warnings at all. What would be a good method for showing warnings? I think it's worth considering. Probably as in other |
Thanks for the feddback
…On Thu, Oct 8, 2020 at 9:32 AM Jukka Paulin ***@***.***> wrote:
@jchapelle <https://github.com/jchapelle>
pytest-dev/pytest#2717 <pytest-dev/pytest#2717>
There's ample talk about whether JUnit reporting structure (the XML
schema) supports warnings at all.
Seems that JUnit has been designed to take a strict stance on every test
resulting either a pass or error; with an additional one state that comes
from the test running environment:
fail = a technical "test running issue" caused the test not to result in
actually reliable information
error = test itself failed
pass = test itself passed
What would be a good method for showing warnings? I think it's worth
considering. Probably as in other
talks about this, one thing to be careful about is that warnings would not
break existing test
setups - otherwise it's gonna be a perhaps (too many) red blips in quality
dashboards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPAMXJV2CR7JRXPBF6X37TSJVTIDANCNFSM4RJNI6GQ>
.
--
Jean Chapelle
|
Would it be possible to display warnings message and their source component ?
The text was updated successfully, but these errors were encountered: