I have followed the link for integrating nunit in TFS as part of TFS build. http://danderson00.blogspot.com/2011/10/running-nunit-tests-under-tfs-build.html using NUNITTFS
It is running the nunit tests and if tests passed passing the build but it is not publishing the test results.
4 projects/solutions compiled
No Test Results
No Code Coverage Results
Impacted Tests
No tests were impacted
Invoke NUnit
C:\Program Files (x86)\NUnit 2.5.9\bin\net-2.0\nunit-console.exe /xml:nunit-tests.xml /framework:net-4.0 Z:\TFSBuilds\1\Sandbox\Tests\Binaries\Tests.dll
00:00
Publish NUnit Results
C:\Program Files (x86)\NUnitTfs\NUnitTfs.exe -n nunit-tests.xml -t Sandbox -p "Any CPU" -f Release -b "Tests_20120213.6" -v 2010
00:00
If NUnit Tests Failed
Any Idea what I am missing now.
Edited:
<client>
<endpoint address="http://mgr:8080/tfs/basecollection/Build/v2.0/BuildService.asmx"
binding="basicHttpBinding" bindingConfiguration="BuildServiceSoap"
contract="BuildServiceV2.BuildServiceSoap" name="BuildServiceSoap" />
<endpoint address="http://mgr:8080/tfs/basecollection/Build/v1.0/PublishTestResultsBuildService2.asmx"
binding="basicHttpBinding" bindingConfiguration="LinkingService"
contract="PublishTestResultsBuildService2V1.LinkingService"
name="LinkingService" />
<endpoint address="http://mgr:8080/tfs/basecollection/Build/v1.0/PublishTestResultsBuildService2.asmx"
binding="basicHttpBinding" bindingConfiguration="Service2Soap"
contract="PublishTestResultsBuildService2V1.Service2Soap"
name="Service2Soap" />
</client>
Your setup seems correct, in other words: it should work.
I have a very similar setup to yours, the only thing that varies against to the one you have is that I include the full path to
nunit-tests.xml. So in my build-log you would see:and
In any case, I would go to the Server that runs the builds and try running the steps by hand in a
CMD.EDIT (after request to deliver my NUnitTFS-config)
Here it is, it seems quite different to yours:
I am hardly the expert here, but what you have as
Build/v2.0/BuildService.asmx, eventually smells like a TFS2008 configuration.