Pavel Vetokhin

> It will. Unfortunately it will not be as easy to use as the rules and TestNG is does not have any extension points like rules. (http://stackoverflow.com/questions/6099633/does-testng-support-something-like-junit4s-rule) Are TestNG listeners...

Thank you for the response. > but it didn't then the failure should already happen during the collection of these artifacts Action `download-artifact` has no [wildcard](https://github.com/actions/download-artifact/issues/6) API. You can download...

I tried idea with assertion step. It works. But I forgot to say about one more subtlety. If application code doesn't change relative to previous run, tests will be skipped...

> I try to understand how fail_check: "${{ needs.testing.result == 'failure' }}" would offer the same capability as counting the artifacts? Testing job fails in presence of not passed tests....

> the action step would just fail? (no other logic associated)? Created check run would just fail, not action step.

Check runs as PR status checks not constrain job structure. That's why I used them. They like lowest common divisor for different workflows and branches. I found [trick](https://boinkor.net/2023/11/neat-github-actions-patterns-for-github-merge-queues/#defining-jobs-that-gather-up-other-jobs-statuses) with defining...

It seems `pull_request.paths` [affected](https://stackoverflow.com/questions/75622889/github-re-triggering-all-checks-on-push-irrespective-of-path) too.

Hi! Unfortunately this is no longer relevant for me.