best practice for backstop test to fail a jenkins build if failure
Open
- Dominant language
- JavaScript
- Stars
- 7.2k
- Forks
- 621
- PR merge metrics
- No merged PRs in 30d
Description
currently, i'm trying out having jenkins run a `backstop test`, output piped to a text file.
and to see whether we should fail the build, i have a bash script that will regex out the number after failure. if it's not equal to 1, the build step fails and developers can then investigate.
is there a better way to do this?
Contributor guide
Assessment
This issue has not been assessed yet.