Skip to content
This repository was archived by the owner on Jun 3, 2026. It is now read-only.

Ensure integration test failures fail the CI build#146

Merged
jgowdy-godaddy merged 2 commits into
mainfrom
bugfixes-round2
Mar 4, 2026
Merged

Ensure integration test failures fail the CI build#146
jgowdy-godaddy merged 2 commits into
mainfrom
bugfixes-round2

Conversation

@jgowdy-godaddy

Copy link
Copy Markdown
Collaborator

Summary

  • Add set -euo pipefail to integration-test.sh (was just set -e)
  • Add explicit || { echo "FAIL: ..."; exit 1; } guards on all four test commands (go test encrypt/decrypt, cucumber-js encrypt/decrypt)

This ensures that if any integration test fails in the future, the CI build fails with a clear error message rather than silently succeeding. Addresses the concern raised in #120.

Test plan

  • Script syntax valid (shellcheck-clean)
  • CI run confirms tests still pass with the stricter error handling

jgowdy added 2 commits March 4, 2026 11:19
Add set -euo pipefail and explicit exit-on-failure guards to all test
commands in integration-test.sh. Prevents silent test failures from
producing a green CI build (fixes #120).
Use ${GOROOT:-} default to handle GOROOT not being set, which is the
case when actions/setup-go already puts go on PATH.
@jgowdy-godaddy
jgowdy-godaddy merged commit 9e77097 into main Mar 4, 2026
2 checks passed
@jgowdy-godaddy
jgowdy-godaddy deleted the bugfixes-round2 branch March 4, 2026 19:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants