Closed elv1s42 closed 1 year ago
@elv1s42 Thanks for the PR. Give me time to analyze the implications in terms of backwards compatibility.
@NikolayPianikov, any updates on this please?
Friendly ping.
Hope that this could be completed soon
Sorry for the delay. My GitHub account was suspended for a while.
hi @NikolayPianikov may I ask when will we have the new release for this? As I see here https://www.nuget.org/packages/NUnit.Extension.TeamCityEventListener The latest version is 1.0.7 from 2019 Will this be included in the newer version of Nunit (which version) or do we have to install it separately?
hi @NikolayPianikov When will the next releases of this project/issue? and When that be included in a release of the NUnit console?
@hn100823 I plan to do it within a week. Yes, you will have to add the package manually until the NUnit.Console package is released
hi @NikolayPianikov, as I see the latest release is from 2019 https://github.com/nunit/teamcity-event-listener/releases Is there any issue?
This is a simple fix for #82 and #84 The idea is that we don't need to use the test name when creating a directory for the artifact. In any case, such artifacts are published into a hidden folder
.teamcity/NUnit/
, so it is enough to use justGuid.NewGuid()
instead of using trimmed test name with escaped special characters.