The 4 v2 scenarios in greet.feature need FEATURE=greet + GODOG_TAGS=@v2 to work. Without that, they fail with 'v2 endpoint not available'. CI doesn't set those, so v2 scenarios are systematically failing in default runs.
Two fixes
Tag 3 untagged v2 scenarios with @v2 @api (one already had it)
Extend DEFAULT_TAGS in run-bdd-tests.sh to exclude @v2
Result
CI default runs pass cleanly. v2 still testable on demand: FEATURE=greet GODOG_TAGS=@v2 go test ./features/greet/...
Companion to PR #26 (BDD_SCHEMA_ISOLATION). Both target CI green for daily PRs.
Diagnosed during the 2026-05-03 trainer day after observing the v2 failures in CI #608.
## Summary
The 4 v2 scenarios in greet.feature need FEATURE=greet + GODOG_TAGS=@v2 to work. Without that, they fail with 'v2 endpoint not available'. CI doesn't set those, so v2 scenarios are systematically failing in default runs.
## Two fixes
1. Tag 3 untagged v2 scenarios with `@v2 @api` (one already had it)
2. Extend DEFAULT_TAGS in run-bdd-tests.sh to exclude `@v2`
## Result
CI default runs pass cleanly. v2 still testable on demand:
`FEATURE=greet GODOG_TAGS=@v2 go test ./features/greet/...`
Companion to PR #26 (BDD_SCHEMA_ISOLATION). Both target CI green for daily PRs.
Diagnosed during the 2026-05-03 trainer day after observing the v2 failures in CI #608.
The 4 v2 scenarios in greet.feature require special config
(FEATURE=greet GODOG_TAGS=@v2) to enable the v2 endpoint via
shouldEnableV2(). Without that config, all v2 scenarios fail
with "v2 endpoint not available".
Two fixes:
1. Tag the 3 untagged v2 scenarios with @v2 @api (one already
had it, others were missing tags)
2. Extend DEFAULT_TAGS in run-bdd-tests.sh to exclude @v2
This makes the default BDD test run pass on CI without v2 setup.
v2 scenarios can still be run explicitly with:
FEATURE=greet GODOG_TAGS=@v2 go test ./features/greet/...
Companion to PR #26 (BDD_SCHEMA_ISOLATION) - both target CI green.
🤖 Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The 4 v2 scenarios in greet.feature need FEATURE=greet + GODOG_TAGS=@v2 to work. Without that, they fail with 'v2 endpoint not available'. CI doesn't set those, so v2 scenarios are systematically failing in default runs.
Two fixes
@v2 @api(one already had it)@v2Result
CI default runs pass cleanly. v2 still testable on demand:
FEATURE=greet GODOG_TAGS=@v2 go test ./features/greet/...Companion to PR #26 (BDD_SCHEMA_ISOLATION). Both target CI green for daily PRs.
Diagnosed during the 2026-05-03 trainer day after observing the v2 failures in CI #608.