Make BDD tests exit code gating in staging workflow #247
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.
The BDD tests in the staging workflow were previously only generating warnings when they failed, with a message indicating that failures were "expected". Since the tests now pass consistently, this PR updates the workflow to properly gate on BDD test failures.
Changes Made
Before:
⚠️ BDD tests failed (this is expected as step definitions are not yet implemented)
bdd_exit_code
variable that didn't affect the overall workflow resultAfter:
❌ BDD tests failed
(no longer suggesting failures are expected)exit_code=1
to fail the entire workflowbdd_result
instead ofbdd_exit_code
)Testing
The workflow logic was validated with test scenarios covering:
The service cleanup and exit code handling remain unchanged, ensuring the staging service is properly stopped regardless of test outcomes.
Fixes #243.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.