From 9cf6e7f1c41d4169c0d5d9122056d1adc6713eae Mon Sep 17 00:00:00 2001 From: Gabriel Radureau Date: Sun, 3 May 2026 12:35:34 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=90=9B=20fix(bdd):=20align=20healthz=20sc?= =?UTF-8?q?enario=20step=20text=20with=20registered=20regex=20(#21)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CI workflow #598 was failing with "Found undefined steps" because the healthz BDD scenario used "the response status code should be 200" while the registered step regex matches "the status code should be N" (without "response"). Aligns the feature wording with the existing convention used in features/auth/. PR #21 généré en autonomie complète par Mistral Vibe (€0.24, 13 steps, 11/13 tool calls success). 3rd autonomous PR du jour. Validation Q-030 workaround : prompt 100% ASCII = pas de hang. Co-authored-by: Gabriel Radureau Co-committed-by: Gabriel Radureau --- features/health/health.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/health/health.feature b/features/health/health.feature index 4985345..81d8ecb 100644 --- a/features/health/health.feature +++ b/features/health/health.feature @@ -13,6 +13,6 @@ Feature: Health Endpoint Scenario: Healthz endpoint returns rich health info Given the server is running When I request the healthz endpoint - Then the response status code should be 200 + Then the status code should be 200 And the response should be JSON with fields "status, version, uptime_seconds, timestamp" And the "status" field should equal "healthy" \ No newline at end of file