test(frontend): add vitest unit tests for the /api/health route handler#88
Open
Moonwalker-rgb wants to merge 1 commit into
Open
test(frontend): add vitest unit tests for the /api/health route handler#88Moonwalker-rgb wants to merge 1 commit into
Moonwalker-rgb wants to merge 1 commit into
Conversation
Follow-up to PR VertexChainLabs#87 (docker: add multi-stage frontend Dockerfile with Next.js standalone output) to ensure the App Router liveness endpoint matches the Docker HEALTHCHECK expectations in docker/frontend.Dockerfile. - Assert GET returns status 200 and application/json content type - Assert the JSON body has status: ok plus an ISO 8601 UTC timestamp - Assert module-level dynamic = force-dynamic export so Next.js does not pre-render the route Refs VertexChainLabs#87
9 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds vitest unit tests for `Frontend/src/app/api/health/route.ts` as a follow-up to PR #87.
The /api/health endpoint is consumed by the Docker HEALTHCHECK directive in `docker/frontend.Dockerfile`, so these tests pin down the contract that the liveness probe depends on. They cover:
Validation performed locally
Refs #87