test: begin API v2 fixture and contract migration - #1
Draft
Optic00 wants to merge 28 commits into
Draft
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
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.
Draft: migrate existing fixtures to API v2.
core.refremains unchanged and unverified; this is not a completed full-suite migration.HTTP fixtures exercise both v2 mounts through real requests. Identity setup retains
/api/auth/me. CLI/MCP fixtures use current response shapes and HTTP workflows. Worklogs check UTC timestamps and persistence; pagination crosses a 101-item boundary.Coverage includes comments, page labels, test management, assets, diagrams, labels, item links, link types, priorities and iterations. Tests retain ownership, role denials, cross-workspace isolation, rejected-write persistence and granular bearer scopes. All nine V1 asset scenarios remain alongside V2 equivalents. Creator-email privacy still requires Core #249; it fails against current unmodified main.
Iteration changes include path-selected scope, local workspace lists, invalid-status rejection and inaccessible-workspace creation returning 404 for nonadmins. Four matrix representatives exercise eight actors on both mounts; this is not complete route-policy coverage.
Frontend fixtures now match current API methods, arrays/envelopes and v2 pagination. Notification acknowledgement remains server-authoritative even when the local inbox looks read. Board tests check automatic background pages with rank/bubble ordering, refresh and workspace changes. Time tests cover overnight durations and equal times representing 24 hours. Updated UI mocks include portal customization, agent connection overview and localized workflow editing; temporary globals are restored.
Latest validation uses main
8608da08plus the two remaining fixes in Core #243. The complete frontend run passes all 1,268 tests in 209 files. The quick suite passes five Go packages and 123 frontend tests. Both targeted Chromium deletion scenarios pass, plus setup, with no skips or retries. PostgreSQL was not rerun in this update.Remaining: legacy
internal/handlerscompile failures, complete route-policy/PostgreSQL/browser coverage and a verified compatibility pin. Keep draft.