-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
TeamCity logger logs warnings as test failures #4591
Labels
Comments
@SvetlanaZem @wbars @epdenouden Can you have a look, please? Thanks! |
This was referenced Mar 16, 2021
sebastianbergmann
pushed a commit
that referenced
this issue
Mar 17, 2021
This was referenced Mar 17, 2021
This was referenced Mar 18, 2021
Merged
Merged
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
Summary
(See https://youtrack.jetbrains.com/issue/WI-57958)
While working on a project making heavy use of
at()
in the test suite I noticed (again) that soft deprecations cause tests to be marked as failed, although the exit code is0
.I've traced this to \PHPUnit\Util\Log\TeamCity::addWarning(), which logs a
testFailed
event.A quick search did not reveal a list of possible event names, so I put a comment in https://youtrack.jetbrains.com/issue/WI-57958 to get help from Jetbrains.
Current behavior
Test cases with warnings are logged with
testFailed
event typeHow to reproduce
Run a test with
at()
matcher orassertRegExp()
or other soft-deprecated features using the--teamcity
command line option:Expected behavior
Use another event name (not
testFailed
), so PhpStorm does not mark the test case as failed.The text was updated successfully, but these errors were encountered: