AFAIK, this is still the same problem as TW-3390. I upgraded to build 6010. I've tried:
{noformat}
- $(MSBuildProjectDirectory)\cps.net\cpstest\**\*Test.dll
- cps.net\cpstest\**\*Test.dll
- $(build_working_dir)\cps.net\cpstest\**\*Test.dll
{noformat}
The last one used to work with the last EAP before 3.0. Stopped working with 3.0.
Either of the wildcard options (1st or 3rd) result in nothing being passed to the NUnit runner. The middle option is passed to the NUnit runner, but it has no abs path prepended to it, so it can't find what it thinks its looking for.
Issue wasresolved
| Old | New | |
| Chris Morris (chrismo) - 10 months ago (21 Jan 2008 13:21) | ||
| Fixed in version | Benares Minor (3.1) | |
| Fixed in version | TeamCity 3.1 (6760) | |
Eugene Petrenko (eugene.petrenko)
10 months ago (16 Jan 2008 11:26)Could you please try to specify relative path to the .sln file folder.
Anyway, please attach a build log or commandline to the TeamCity tests runner.
Thanks!
Eugene Petrenko (eugene.petrenko)
10 months ago (16 Jan 2008 12:13){noformat}
What did you mean as '***' (3 stars)
in your wildcard?
Could you please try to replace it with something line
"\**\*" (slash-2-stars-slash-star) or "*\**\" (star-slash-2-star-slash)
{noformat}
Sorry, Jira Wiki-formatter changed the text presentation.
Thanks!
Chris Morris (chrismo)
10 months ago (19 Jan 2008 01:25)Sorry, late in getting back to you.
The three asterisks I guess was a formatting issue from a comment you'd made on TW-3390 - I'd only tried it because that's what I thought you'd asked me to try inside that issue - but I've never had that work for me (and thought it was odd at the time).
I'm not sure what you mean by "Could you please try to specify relative path to the .sln file folder." I will try to attach log output here in a bit.
Chris Morris (chrismo)
10 months ago (19 Jan 2008 01:40)Ok, I think I understand. If my "Solution file path:" is
Then I guess I could just do:
...trying it now.
Chris Morris (chrismo)
10 months ago (19 Jan 2008 01:48)This is the output from the build log:
Using "NUnitTeamCity" task from assembly "C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MSBuildLoggers.dll".
Command:
C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher2.0.exe
The "NUnitTeamCity" task is using "JetBrains.BuildServer.NUnitLauncher2.0.exe" from "C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher2.0.exe".
TeamCity NUnit 2.2 Runner Copyright (C) 2007 JetBrains s.r.o. by Eugene Petrenko and Mikhail Pilin
Usage:
Chris Morris (chrismo)
10 months ago (19 Jan 2008 01:59)Hold on - there's no Test assemblies down that directory structure. Now I'm trying:
Chris Morris (chrismo)
10 months ago (19 Jan 2008 02:08)That's working now :-) Excellent. Sorry for the confusion, I guess I just didn't read up on the official changes for the NUnit runner, and the path needing to be relative to the .sln file folder.
Eugene Petrenko (eugene.petrenko)
10 months ago (21 Jan 2008 13:21)I have created as issue to workatound the problem. Please watch TW-4290 for details. Thanks!