fix(ci): add explicit markers to BDD and post-deploy pytest runs - #334
Merged
Conversation
Same class of bug as the acceptance-check job: the pytest.ini default -m 'unit or integration' deselects BDD tests (auto-marked e2e) and acceptance tests (auto-marked acceptance), producing exit code 5 (zero tests collected) and failing main's Tier 2 governance guard.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Main's Tier 2 governance run fails with exit code 5 on the BDD acceptance step:
Same latent bug in the post-deployment workflow's acceptance step.
Root cause
The testing-pyramid restructure (#332) set pytest.ini addopts to
-m 'unit or integration'so a barepytestis safe-by-default. conftest auto-markstests_bdd/ase2eandtests/acceptance/asacceptance— so without an explicit marker override, both commands collect zero tests and pytest exits 5.Fix
docker-publish.yml: BDD step →pytest tests_bdd/ -q --tb=short -m e2epost-deployment.yml: acceptance step →pytest tests/acceptance/ -q --tb=short -v -m acceptanceThis is the same fix already applied to the ci-quality acceptance job. Merge this first so main's Tier 2 governance goes green and the Main CI Guard unblocks other PRs.