🐛 fix(bdd): exclude @v2 scenarios from default BDD test runs #27

Merged
arcodange merged 1 commits from fix/exclude-v2-from-default-bdd into main 2026-05-03 13:59:27 +02:00

1 Commits

Author SHA1 Message Date
6b39d3c3c9 🐛 fix(bdd): exclude @v2 scenarios from default BDD test runs
All checks were successful
CI/CD Pipeline / Build Docker Cache (push) Successful in 25s
CI/CD Pipeline / CI Pipeline (push) Successful in 7m37s
CI/CD Pipeline / Trigger Docker Push (push) Has been skipped
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) <noreply@anthropic.com>
2026-05-03 13:59:11 +02:00