-
Notifications
You must be signed in to change notification settings - Fork 52
LCORE: 490 - Add e2e tests for health endpoints #445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tisnik
merged 1 commit into
lightspeed-core:main
from
radofuchs:LCORE_490_Health_endpoints_e2e
Aug 25, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,53 +1,64 @@ | ||
| # Feature: Health endpoint API tests | ||
| #TODO: fix test | ||
|
|
||
| # Background: | ||
| # Given The service is started locally | ||
| # And REST API service hostname is localhost | ||
| # And REST API service port is 8080 | ||
| # And REST API service prefix is /v1 | ||
|
|
||
|
|
||
| # Scenario: Check if service report proper readiness state | ||
| # Given The system is in default state | ||
| # When I access endpoint "readiness" using HTTP GET method | ||
| # Then The status code of the response is 200 | ||
| # And The body of the response has the following schema | ||
| # """ | ||
| # { | ||
| # "ready": "bool", | ||
| # "reason": "str", | ||
| # "providers": "list[str]" | ||
| # } | ||
| # """ | ||
| # And The body of the response is the following | ||
| # """ | ||
| # {"ready": true, "reason": "All providers are healthy", "providers": []} | ||
| # """ | ||
|
|
||
| # Scenario: Check if service report proper readiness state when llama stack is not available | ||
| # Given The system is in default state | ||
| # And The llama-stack connection is disrupted | ||
| # When I access endpoint "readiness" using HTTP GET method | ||
| # Then The status code of the response is 503 | ||
|
|
||
| # Scenario: Check if service report proper liveness state | ||
| # Given The system is in default state | ||
| # When I access endpoint "liveness" using HTTP GET method | ||
| # Then The status code of the response is 200 | ||
| # And The body of the response has the following schema | ||
| # """ | ||
| # { | ||
| # "alive": "bool" | ||
| # } | ||
| # """ | ||
| # And The body of the response is the following | ||
| # """ | ||
| # {"alive":true} | ||
| # """ | ||
|
|
||
| # Scenario: Check if service report proper liveness state when llama stack is not available | ||
| # Given The system is in default state | ||
| # And The llama-stack connection is disrupted | ||
| # When I access endpoint "liveness" using HTTP GET method | ||
| # Then The status code of the response is 503 | ||
| Feature: REST API tests | ||
|
|
||
|
|
||
| Background: | ||
| Given The service is started locally | ||
| And REST API service hostname is localhost | ||
| And REST API service port is 8080 | ||
| And REST API service prefix is /v1 | ||
|
|
||
|
|
||
| Scenario: Check if service report proper readiness state | ||
| Given The system is in default state | ||
| When I access endpoint "readiness" using HTTP GET method | ||
| Then The status code of the response is 200 | ||
| And The body of the response has the following schema | ||
| """ | ||
| { | ||
| "ready": "bool", | ||
| "reason": "str", | ||
| "providers": "list[str]" | ||
| } | ||
| """ | ||
| And The body of the response is the following | ||
| """ | ||
| {"ready": true, "reason": "All providers are healthy", "providers": []} | ||
| """ | ||
|
|
||
|
|
||
| Scenario: Check if service report proper liveness state | ||
| Given The system is in default state | ||
| When I access endpoint "liveness" using HTTP GET method | ||
| Then The status code of the response is 200 | ||
| And The body of the response has the following schema | ||
| """ | ||
| { | ||
| "alive": "bool" | ||
| } | ||
| """ | ||
| And The body of the response is the following | ||
| """ | ||
| {"alive": true} | ||
| """ | ||
|
|
||
|
|
||
| Scenario: Check if service report proper readiness state when llama stack is not available | ||
| Given The system is in default state | ||
| And The llama-stack connection is disrupted | ||
| When I access endpoint "readiness" using HTTP GET method | ||
| Then The status code of the response is 503 | ||
| And The body of the response, ignoring the "providers" field, is the following | ||
| """ | ||
| {"ready": false, "reason": "Providers not healthy: unknown"} | ||
| """ | ||
|
|
||
|
|
||
| Scenario: Check if service report proper liveness state even when llama stack is not available | ||
| Given The system is in default state | ||
| And The llama-stack connection is disrupted | ||
| When I access endpoint "liveness" using HTTP GET method | ||
| Then The status code of the response is 200 | ||
| And The body of the response is the following | ||
| """ | ||
| {"alive": true} | ||
| """ | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.