3 Commits

Author	SHA1	Message	Date
Gabriel Radureau	70c2eb554e	🧪 test: implement per-scenario state isolation and enhance validate-test-suite.sh ... - Add pkg/bdd/steps/scenario_state.go with thread-safe per-scenario state manager - Update auth_steps.go, jwt_retention_steps.go to use per-scenario state accessors - Add LastSecret and LastError fields to ScenarioState for JWT retention testing - Update steps.go with SetScenarioKeyForAllSteps function - Update suite.go to generate scenario keys and clear state properly - Mark config hot-reload scenarios as @flaky (timing-sensitive) - Fix validate-test-suite.sh: add -p 1 flag for sequential execution, filter JSON logs, add --count flag - Add CONFIG_SCHEMA.md documenting configuration architecture - Split greet tests into v1/v2 sub-tests with explicit v2 enable/disable Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>	2026-04-11 13:34:51 +02:00
Gabriel Radureau	25a20d4380	📝 docs: add ADR 0025 documenting BDD scenario isolation strategies ... - Document 5 considered options for BDD test isolation - Analyze pros/cons of each approach (transaction rollback, clear tables, schema-per-scenario, database-per-feature, combined) - Explain Gherkin Background behavior and implications - Detail critical limitation: PostgreSQL schemas don't isolate in-memory state - Recommend enhanced multi-layer isolation strategy - Document cache key prefix/suffix approach for future cache integration - Add schema and cache key naming conventions - Reject explicit Background setup approach as error-prone and unscalable Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>	2026-04-11 07:57:46 +02:00
Gabriel Radureau	0aedf829de	✨ feat: implement schema-per-scenario isolation for BDD tests ... - Add BDD_SCHEMA_ISOLATION env var to enable schema-per-scenario mode - Generate unique schema names using SHA256 hash of feature+scenario - Implement SetupScenarioSchema() and TeardownScenarioSchema() methods - Handle search_path configuration for schema isolation - Use CASCADE drop to clean up all scenario-created DB objects - Add isSchemaIsolationEnabled() helper to suite.go - Update cleanup flow: skip table clearing when schema isolation is active - Add ADR 0025 documenting isolation strategies and decision rationale Activation: Set BDD_SCHEMA_ISOLATION=true to enable Debug: Set BDD_ENABLE_CLEANUP_LOGS=true for verbose isolation logging Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>	2026-04-10 22:46:02 +02:00