VSTest will try to run tests even if none are present in the project. If a project does not have any tests this will result in an unstable result for a Jenkins job that includes the VSTest Runner plugin.

Our use case is that we have a shared library for all .NET projects. Some of the projects have tests and some do not. We would like to not have to configure each Jenkins job to tell if it has tests or not. Instead we wnat the VSTest Runner plugin to be able to skip tests if there are no tests files.

Unfortunately that is not possible using only the command line application vstest.console.exe.