TeamCity v6.0.1 NUnit Build step with NCover: How do I input a path to an assembly with a space in it?

Hey,

I have been trying in vain to enter the following path into the NUnit 'Run tests from' GUI field:

%system.teamcity.build.checkoutDir%\Web Applications\blablablabla\morebla\something.dll

No matter what derivation of the input path I use I get the following in the build log:

NCover Complete v3.4.14.6908 x86 (Administrator)

...
[10:33:38]: The executable can not be located at: 'Applications\blablablabla\morebla\something.dll'
[10:33:38]: Process exited with code 20000


I have tried encasing the entire path with "s and 's and I have tried replacing the Web Applications with ** and still get the same result.  Any ideas on how to get the path to work?


Cheers,
Andrew


PS I am using NCover 3.x in the build step which is why the error is reporting by NCover.
PPS Interesingly although the process exists with code 20000 the build configuration still passes, possible bug?
5 comments
Comment actions Permalink

Hi Andrew

How do you configure NCover options? Could you post a screenshot please.
If assembly names are specified there, they should be quoted too.

Michael

0
Comment actions Permalink

Here is my NUnit/NCover setup, given the setup runs no tests I presume the problem is in the first image, although once that is solved the cover could have a problem for the same reason:

NUnitSetup.PNG

NCoverSetup.PNG

Cheers,
Andrew

0
Comment actions Permalink

Hi Andrew

I confirmed a bug and filled TW-15493, you can watch for it.

Thanks
Michael

0
Comment actions Permalink

Hey Michael,

Thanks for investigating and raising the issue, I've voted and am watching.  Does your dev team only work on highly voted for items or is there a chance this will get in?

Cheers,
Andrew

PS I'm not sure whether to mark this as a correct answer given that a bug was confirmed?

0
Comment actions Permalink

Andrew,

We're continuously looking at votes in our tracker, especially for feature requests.
But this particular issue is a bug, so it gets higher priority regardless of votes.
I cannot promise you a specific date right now, but we classified it as "major", so will look into it in nearest time possible.

Thanks
Michael

0

Please sign in to leave a comment.