Conversation
routes/routes_test.go:263 had TestRouteServiceMethods/HealthCheckRoutes
disabled with t.Skip("Health check test requires a properly
initialized pool"). The skip was overcautious — HealthCheckRoutes
itself only decides whether to register the /health-check route
(if r.pool != nil ...); it does not exercise the pool. Registration
can be verified without a working DB.
Replace the skip stub with a struct-table subtest covering both
branches of the guard:
- nil pool → /health-check must NOT be registered (safe default when
the service starts without a working DB)
- non-nil pool → /health-check MUST be registered
Each case builds a fresh RouteService and calls HealthCheckRoutes(),
then asserts on ee.Routes(). Handler behavior itself is exercised
by controllers/health_check_test.go and is out of scope here.
Up to standards ✅🟢 Issues
|
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
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.
routes/routes_test.go:263 had TestRouteServiceMethods/HealthCheckRoutes
disabled with t.Skip("Health check test requires a properly
initialized pool"). The skip was overcautious — HealthCheckRoutes
itself only decides whether to register the /health-check route
(if r.pool != nil ...); it does not exercise the pool. Registration
can be verified without a working DB.
Replace the skip stub with a struct-table subtest covering both
branches of the guard:
the service starts without a working DB)
Each case builds a fresh RouteService and calls HealthCheckRoutes(),
then asserts on ee.Routes(). Handler behavior itself is exercised
by controllers/health_check_test.go and is out of scope here.