jest-coverage-report-action

jest-coverage-report-action copied to clipboard

Idea

When jest exits with non-zero exit code, action always treats that as "crash". However, it is not always the case. Situations, when tests failed, or coverage threshold not passed, should be treated as normal behavior, and not comment that jest "crashed".

Description

I think the "crash" could be detected, when report.json file is not generated.

Additional context

Originally suggested by @dstoyanoff in https://github.com/ArtiomTr/jest-coverage-report-action/issues/222#issuecomment-1022185999