We have a few build definitions that run different subsets of tests based on the categories they are in. This means that for some definitions the assemblies included in the path have no tests which match the category being used.
For some reason this is reported as the dll being an 'ignored' test. I don't consider this to be an ingored test, whilst I'm happy to see log someone that says 'this dll had no tests matching criteria' I don't want to see it counting as ignored because that has a very specific meaning in terms of nunit. Eg a test that was explicitly set to ignored for some reason.
Is this something that nunit is reporting to teamcity? is there any way (without dynamically figuring out which dlls not to use) to stop these from being reported as ignored?