Split the large syncer test suite into focused test files#20
Merged
Conversation
Tasks: - T20260510-21: Split the large syncer test suite into focused test files
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.
Task
T20260510-21 — Split the large syncer test suite into focused test files
Description
Problem
internal/sync/syncer_test.gois over 1,000 lines and includes fake repositories/config stores/state stores, environment setup, push tests, dry-run tests, cancellation tests, pull verification tests, workspace-reference tests, and commit-message tests. The size makes test failures harder to navigate and increases merge-conflict risk for unrelated sync work.Why It Matters
Moving shared fakes/helpers and scenario groups into focused test files lets multiple sync changes land with less contention. It also makes the production sync refactor task safer because the test cleanup can happen independently.
Constraints / Notes
Acceptance Criteria
internal/sync/syncer_test.gois split into focused test files and no single remaining sync test file owns all fakes, setup, push, pull, workspace-reference, and commit-message coverage together.go test -v ./internal/syncpasses.go test -v ./internal/...passes.Execution Summary
Click to expand
Outcome: success
Changes:
Validation:
Assessment: Behavior-preserving test-only refactor; both required validation commands pass.
Validation
Branch Freshness
origin/mainorbit/T20260510-21-6a00ea9bauthored by: gpt-5