Add Trip Editor error-state contract coverage#300
Merged
Conversation
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.
Summary
Implements #297 Batch 3 only: Trip Editor stale/error/dirty/delete feedback contracts.
Claim Boundary
These tests intentionally use mocked non-2xx mutation responses for hard-to-trigger browser failure states. They prove frontend failure feedback and state preservation only. They do not claim CRUD persistence proof.
Batch 2 real endpoint specs cover successful delete/removal/persistence. This PR does not duplicate that success proof.
Out Of Scope
Validation
dotnet build: passed.dotnet test: passed, 1537 tests.git diff --check origin/main...HEAD: passed.