test(api): route-handler tests for ticket transitions#51
Merged
Conversation
Covers applyTicketTransition directly (fake db/ctx, mirroring the visitor route tests): 404 on missing, 409 on illegal transitions, and the start/resolve/close/reopen/cancel success paths incl. extra set values.
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.
Hardens the maintenance-tickets vertical with handler-level tests for
applyTicketTransition(previously only the pure state machine was unit-tested).Mirrors the existing visitor route-test pattern (fake Drizzle client + fake Context): 404 on a missing ticket, 409 on illegal transitions, and the start/resolve/close/reopen/cancel success paths — including that the
extraset values (e.g.resolutionNote) are persisted.6 new tests (104 API tests total); full gate green.