This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Added flag to fail execution when no test classes exist for specified manifest and/or regex only if it's set to true #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when no test class is found for specified manifest and/or regex, then the execution fails. I've added a flag
-require.at.least.one.test
which doesn't fail the execution in such a scenario unless it's set totrue
(which is a default value).Motivation: our case is that we are running tests while validating Pull Requests in our CI/CD pipeline and we are running only these tests which have changed or which source classes have changed, e.g. when
MyClassApex
has changed, then we are running testMyClassApexTest
. We are simply appending 'Test' to the class name (by convention) but not all classes have tests and in such a situation, we don't want to fail the build.Feel free to merge, maybe someone will have a similar situation to ours :)