Gabriel Radureau
9cf6e7f1c4
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>
18 lines
653 B
Gherkin
18 lines
653 B
Gherkin
# features/health.feature
|
|
@health @smoke @critical
|
|
Feature: Health Endpoint
|
|
The health endpoint should indicate server status
|
|
|
|
@basic @critical
|
|
Scenario: Health check returns healthy status
|
|
Given the server is running
|
|
When I request the health endpoint
|
|
Then the response should be "{\"status\":\"healthy\"}"
|
|
|
|
@basic @critical
|
|
Scenario: Healthz endpoint returns rich health info
|
|
Given the server is running
|
|
When I request the healthz endpoint
|
|
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" |