Files

Gabriel Radureau dbadff58e2 🔍 feat(bdd): add state tracer and fix config reload timing

- Add STATE_TRACER_README.md with full documentation
- Add state_tracer.go for per-process BDD execution tracing to $TMPDIR
- Integrate tracing hooks in suite.go (SCENARIO_START/END, JWT_RESET, DB_CLEANUP)
- Fix config_steps.go: increase file recreation delay to 1100ms for 1s polling interval
- Fix config_test.go: update expected values to match current implementation
- Document findings: sequential per-feature execution, shared DB, in-memory JWT secrets
- Identify root causes of intermittent failures

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>

2026-04-11 10:25:27 +02:00

auth_steps.go

🧪 fix: implement JWT secret cleanup and stabilize BDD test suite

2026-04-10 16:06:21 +02:00

common_steps.go

🧪 test: add comprehensive BDD test suite for user authentication

2026-04-09 00:25:48 +02:00

config_steps.go

🔍 feat(bdd): add state tracer and fix config reload timing

2026-04-11 10:25:27 +02:00

greet_steps.go

🧪 test: implement comprehensive BDD test suite for JWT secret rotation

2026-04-09 22:51:19 +02:00

health_steps.go

🧪 test: add comprehensive BDD test suite for user authentication

2026-04-09 00:25:48 +02:00

jwt_retention_steps.go

🔍 feat(bdd): add state tracer and fix config reload timing

2026-04-11 10:25:27 +02:00

README.md

🧪 test: add comprehensive BDD test suite for user authentication

2026-04-09 00:25:48 +02:00

steps.go

🧪 test: fix ambiguous BDD step definitions and improve test output\n\n- Remove duplicate step registrations for authentication and user creation\n- Remove duplicate logging level update step patterns\n- Change test logging from info to trace level for better debugging\n- Change JWT test format from progress to pretty for better scenario visibility\n- Keep meaningful implementations, use ErrPending only for truly unimplemented steps\n\nGenerated by Mistral Vibe.\nCo-Authored-By: Mistral Vibe <vibe@mistral.ai>

2026-04-10 08:42:46 +02:00

steps.go.backup

🧪 test: reduce BDD undefined steps from 52 to 1

2026-04-09 17:40:51 +02:00

README.md

BDD Steps Organization

This folder contains the step definitions for the BDD tests, organized by domain for better maintainability and scalability.

Structure

pkg/bdd/steps/
├── greet_steps.go        # Greet-related steps (v1 and v2 API)
├── health_steps.go       # Health check and server status steps
├── auth_steps.go         # Authentication and user management steps
├── common_steps.go       # Shared steps used across multiple domains
├── steps.go             # Main registration file that ties everything together
└── README.md            # This file

Design Principles

Domain Separation: Steps are grouped by functional domain
Single Responsibility: Each file focuses on a specific area of functionality
Reusability: Common steps are shared via common_steps.go
Scalability: Easy to add new domains as the application grows

Adding New Steps

For new domains: Create a new *_steps.go file following the existing pattern
For existing domains: Add to the appropriate domain file
For shared functionality: Add to common_steps.go
Register all steps: Update steps.go to include the new steps

Step Naming Convention

Use descriptive, action-oriented names
Follow the pattern: i[Action][Object] or the[Object][State]
Example: iRequestAGreetingFor, theAuthenticationShouldBeSuccessful

Testing the Steps

Run BDD tests with:

go test ./features/... -v

Future Domains

As the application grows, consider adding:

payment_steps.go - Payment processing steps
notification_steps.go - Notification and email steps
admin_steps.go - Admin-specific functionality steps
api_steps.go - General API interaction patterns