test: add end-to-end integration tests for auth and delivery flows - #80
Open
AdaBebe0 wants to merge 1 commit into
Open
test: add end-to-end integration tests for auth and delivery flows#80AdaBebe0 wants to merge 1 commit into
AdaBebe0 wants to merge 1 commit into
Conversation
Adds two integration suites under tests/integration/ that chain real HTTP requests through the full Controller -> Service -> Model stack against a live MongoDB instance (mongodb-memory-server), complementing the existing per-endpoint tests in tests/*.test.ts. auth.flow.integration.test.ts: register -> login -> reuse the issued JWT against a real protected route, covering both the success path and error conditions (unknown account, duplicate registration, insufficient role, tampered token, missing token). delivery.flow.integration.test.ts: carries a single delivery through create -> read -> update -> archive -> restore against the CRUD model, and separately walks a delivery through every valid status transition (pending -> assigned -> picked_up -> in_transit -> delivered) as an authenticated driver against the status-transition endpoint. The two endpoint groups are exercised independently and documented as such, since they currently operate on two distinct Mongoose models (src/models/Delivery.ts vs src/models/deliveryModel.ts) despite sharing the /api/v1/deliveries prefix. No inline mocks or hardcoded response data are used; only the logger is mocked. All assertions read back real persisted state from Mongo.
|
@AdaBebe0 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Adds two integration suites under tests/integration/ that chain real HTTP requests through the full Controller -> Service -> Model stack against a live MongoDB instance (mongodb-memory-server), complementing the existing per-endpoint tests in tests/*.test.ts.
auth.flow.integration.test.ts: register -> login -> reuse the issued JWT against a real protected route, covering both the success path and error conditions (unknown account, duplicate registration, insufficient role, tampered token, missing token).
delivery.flow.integration.test.ts: carries a single delivery through create -> read -> update -> archive -> restore against the CRUD model, and separately walks a delivery through every valid status transition (pending -> assigned -> picked_up -> in_transit -> delivered) as an authenticated driver against the status-transition endpoint. The two endpoint groups are exercised independently and documented as such, since they currently operate on two distinct Mongoose models (src/models/Delivery.ts vs src/models/deliveryModel.ts) despite sharing the /api/v1/deliveries prefix.
No inline mocks or hardcoded response data are used; only the logger is mocked. All assertions read back real persisted state from Mongo.
closes #57