Remco;12306 wrote:There isn't any built-in way of doing this, other than making sure all the tests get run (perhaps through the 'ignored tests' configuration)
...
This can actually be a valid error case if someone has a filter that goes wrong or there are important grid nodes offline.
In my case it is also valid since I have both explicit tests, HTTP integration tests (filtered via category), long running tests (category), performance tests (category) etc. which I don't want to be run as part of my "build on commit" CI config.
I also have a bunch of explicitly ignored tests we simply don't want to spend time on fixing right now.
Remco;12306 wrote:
I would recommend wrapping the call to the console tool in a batch file or powershell script that can intercept the result and return something else to TeamCity.
But it isn't the exit code that is the problem (which is #0), but it is the error reported by NCRunch as a TC service message.