-
Notifications
You must be signed in to change notification settings - Fork 746
Test has passed however Reason with an empty message is printed in the xml #1896
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
Comments
The fact that TeamCity reports a passed test as a failure is a problem that should be fixed there. @NikolayPianikov any comments on that? What about @psandhu79 can you give us a code example of a test that displays an empty message? |
@rprouse Thank you looks like a bug in TeamCity found this However the tests pass in Nunit 2 for teamcity and fail in Nunit 3 i am guessing its a regression in the Nunit importer for the xml |
Even if it is not the cause of the TC errror, NUnit should not be creating an empty reason element under any circumstance. We need to confirm whether this happens, and when, and fix it. Based on the TC issue, it appears to happen when AssertPass is used. We should check out Assert.Pass both with and without a message. |
TC reports a failed test either with Assert.Pass() or Asset.Pass("No exception should occur until this point with current setup") With a message the reason element contains the message |
There should only be a reason element if there is a reason. Of course, TC should deal with it anyway, but we should fix our output as well. |
@psandhu79 it looks like a bug in the TeamCity xml parser for NUnit. I will check it |
@NikolayPianikov could you please update this bug If possible attached a new xml plugin and i can test we are using TC 10.0.2 |
@psandhu79 I can't reproduce this issue. Could you attach nunit xml report file? |
@psandhu79 Looks like this issue was fixed in TeamCity 10.0.3 |
I'll pick this one up - hopefully have a fix in the next few days. |
Great! Looking forward to seeing it. |
Fixed by #1955 |
This when imported into TeamCity reports a failure
The text was updated successfully, but these errors were encountered: