- Fixed path resolution in test setup to handle both feature-specific and multi-feature execution
- Standardized stopOnFailure=false for all feature tests to ensure consistent behavior
- Removed @todo tag from implemented Configuration validation scenario
- Ensured GODOG_TAGS=todo go test ./features/X/... and FEATURE=X go test ./features/ run identical tests
All feature suites (jwt, auth, greet, health, config) now behave consistently regardless of execution method.
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
- Create pkg/bdd/testsetup package with shared test configuration functions
- Refactor all feature test files to use shared setup (70+ lines reduced)
- Implement dynamic feature path detection by scanning filesystem for directories
- Add getProjectRoot() function to find project root via go.mod
- Maintain all existing functionality (tags, stop on failure, etc.)
- Add fallback to hardcoded paths if filesystem access fails
- Sort feature paths for consistent test execution order
Before: ~35 lines per test file with duplicated setup code
After: ~5 lines per test file using shared functions
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistralai.com>
