Skip to content

History / Testing Scenarios

Revisions

  • docs(scenarios): refresh Testing-Scenarios for git-scenarios 0.5.0 The page was written when the package was at v0.3.0/0.3.1 with 19 scenarios; the registry has grown to 27 across the v0.3.2 → v0.5.0 releases and the package now exposes a Jest framework adapter plus programmatic registration. Brought the page back in sync. Changes: - Total bumped 19 → 27 across the kind tables. - Added missing scenarios that landed since the original draft: empty-repo (0.3.2), branch-sync-showcase (0.3.3), mid-rebase-conflict + mid-cherry-pick-conflict (0.4.0), multiple-worktrees + shallow-clone + large-repo + mid-revert-conflict (0.5.0). - Rewrote the in-progress operations section to surface the complete conflict matrix (merge / rebase / cherry-pick / revert) with each state's .git/ marker file. - New "I'm working on the conflicts view" workflow block calls out the four-scenario cycle as the right way to audit any conflict-view changes. - New "stress-test history" + "worktrees view" workflow blocks for large-repo and multiple-worktrees. - New "Path A — the Jest framework adapter" section describing describeWithScenario / describeEachScenario / describeWithScenarioExtended as the preferred surface for new tests. The raw spinUpScenario API becomes Path B for cases that need finer lifecycle control. - New "Path B — fromScenario" + "Path C — register a coco-specific scenario at runtime" sections in the "compose your own" guide. - "Where things live" mentions the Jest adapter subpath export and the bin/scenarioRunner.ts wrapper that makes --run-ui work. Home.md tile copy refreshed to match: 19 → 27, conflict matrix language ("merge / rebase / cherry-pick / revert"), describeWithScenario swapped in for the older spinUpScenario one-liner.

    @gfargo gfargo committed May 22, 2026
  • docs: add Testing-Scenarios page Comprehensive guide to coco's scenario library: - The 19 named scenarios available, grouped by kind - The npm run scenario CLI (list, describe, create + flags) - Common dev workflows for each TUI surface (chip-rendering-showcase, mid-merge-conflict, branch-diverged, etc) - How to compose scenarios inline in tests via the atom layer - How to use spinUpScenario in jest integration tests - Pointers to the @gfargo/git-scenarios package for contributing new scenarios back Also surfaces the page on Home.md so it's discoverable from the landing index.

    @gfargo gfargo committed May 18, 2026