🐛 fix(bdd): align healthz scenario step text with registered regex (#21)

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 <arcodange@gmail.com>
Co-committed-by: Gabriel Radureau <arcodange@gmail.com>
This commit was merged in pull request #21.
This commit is contained in:
2026-05-03 12:35:34 +02:00
committed by arcodange
parent 045823ec8e
commit 9cf6e7f1c4

View File

@@ -13,6 +13,6 @@ Feature: Health Endpoint
Scenario: Healthz endpoint returns rich health info Scenario: Healthz endpoint returns rich health info
Given the server is running Given the server is running
When I request the healthz endpoint 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 response should be JSON with fields "status, version, uptime_seconds, timestamp"
And the "status" field should equal "healthy" And the "status" field should equal "healthy"