-
Notifications
You must be signed in to change notification settings - Fork 11
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
Colon's in testcase data are replaced with <space> in the Teamcity service messages #68
Comments
This is likely to be a bug in the teamcity extension but to be sure, can you tell us what the name of the test case is in the XML result? |
Below is an output from the latest console/teamcity extension which outputs both the NUnit Console's labels, and the TeamCity messages. From this, the problem appears to lie in the teamcity extension - I'll transfer this issue over shortly. 🙂
|
@chrisgeorge0911 unfortunately I have to replace the colon symbol because of TeamCity treats it as a delimiter of an assembly name and a test class/method name. As alternative I could replace it by '%3A' for instance. But in your test report you will see the line like |
@NikolayPianikov how about replacing ":" with "<colon>"? My worry with "%3A" is that its more likely to be used as a parameter along with specifying the actual ":" character. "<colon>" is very unlikely to be used as a parameter, but would still uniquely identify that particular test case. |
@chrisgeorge0911 Ok, I will add the environment variable to specify the value for this replacement and by default it will be "". Thank you |
Sounds great 👍 thanks |
Fix will be available in NUnit.Extension.TeamCityEventListener 1.0.7 |
For reference, as this isn't currently anywhere on the net, the environment variable you can use to override the default |
Nunit 3.11 / Nunit console 3.10
Having a simple parameterised testcase such as
Runs fine, but with --teamcity, the resulting teamcity service messages look like:
Notice the lack of colon's in the test1 lines.
This becomes a problem when there are other parameterised tests that actually pass a space, because teamcity underreports the number of issues as they are not unique.
The text was updated successfully, but these errors were encountered: