Added option to fail the build if no tests were run

[pakore]

This will enable an option in the configuration to fail the tests if not a single test was run.
Also it will output in the log
[xUnit] [ERROR] - All test reports are empty.

The use case for this is the following:

• A job run some unit tests (e.g. GTest) with a filter (--gtest-filter=WhateverSuite.testThatDo*)
• A developer renames the unit tests and these tests fall out of the filter
• The job runs, executes 0 tests and build is SUCCESS even though tests may not pass.

With this PR, the job will fail if there are no tests to run.

[Jimilian]

@pakore can you fix the conflicts, please? This plugin finally has a new maintainer, so, we can hope to get this change merged in.

[nfalco79]

Why did you choose to put it this as an extra configuration? All settings of that kind (like skipIfEmpty, failIfNotNew, stopProcessingIfError) are related to the "Tools type".

Could be the same concept of skip if no test file exists? Which tool other than GTest produce an empty report file also if no tests was run?

[nfalco79]

Actually this was implemented with the new passed threshold where you can set a minimun number of passed test or the build is considered UNSTABLE/FAILED