Files
backnotprop__plannotator/tests
Michael Ramos 472e17be3d feat: expandable diff context in code review (#247)
* feat: expandable diff context in code review (closes #243)

Switch from PatchDiff to FileDiff component from @pierre/diffs to enable
GitHub-style "show more lines" buttons between hunks. The library handles
all expansion UI when provided full file contents via oldLines/newLines.

- Add /api/file-content endpoint to serve old/new file content per diff type
- Add getFileContentsForDiff() helper with ref mapping for all diff types
- Parse patch client-side via getSingularPatch(), augment with file contents
- Update @pierre/diffs from 1.0.4 to 1.0.11 (scroll sync fix, no breaking changes)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: upgrade @pierre/diffs to beta, re-parse patch with full file contents

The previous approach spread file content arrays onto a partial-mode
FileDiffMetadata, causing hunk index mismatches and Shiki decoration
errors. Now uses processFile() to re-parse the patch with oldFile/newFile
so hunk indices are computed against the full file (isPartial: false),
which is required for expansion to work correctly.

Also fixes a flash error on file switch by tagging fileContents with the
filePath they were fetched for, preventing stale contents from being
paired with the wrong patch during the render before useEffect fires.

- Upgrade @pierre/diffs from ^1.0.x to ^1.1.0-beta.19 in all workspaces
- Add test fixtures for disjoint hunks, deleted/renamed/new files

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: abort stale file-content fetches, validate path params

- Add AbortController to file-content fetch effect to cancel in-flight
  requests when switching files
- Reject path traversal (.. or absolute paths) on /api/file-content
- Document /api/file-content endpoint in CLAUDE.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-08 14:00:43 -07:00
..

Tests

This directory contains manual testing scripts for Plannotator.

UI Tests (manual/local/)

These scripts test the UI components and require a browser.

Plan review UI:

./tests/manual/local/test-hook.sh          # Claude Code simulation
./tests/manual/local/test-hook-2.sh        # OpenCode origin badge test

Code review UI:

./tests/manual/local/test-opencode-review.sh  # Code review UI test
./tests/manual/local/test-worktree-review.sh  # Worktree support test (creates sandbox with 4 worktrees)

See UI-TESTING.md for detailed UI testing documentation.

Integration & Utility Tests (manual/local/)

These scripts test integrations, releases, and provide utilities.

Binary release testing:

./tests/manual/local/test-binary.sh        # Test installed binary from ~/.local/bin/

Tests the installed plannotator binary to verify releases work correctly.

Bulk plan testing (Obsidian integration):

./tests/manual/local/test-bulk-plans.sh    # Iterate through ~/.claude/plans/

Opens each .md file from ~/.claude/plans/ in Plannotator. Great for testing Obsidian integration with multiple plans.

OpenCode integration sandbox:

./tests/manual/local/sandbox-opencode.sh [--disable-sharing] [--keep] [--no-git]

Creates a temporary sandbox with a sample React/TypeScript project, initializes git with uncommitted changes, sets up the local OpenCode plugin, and launches OpenCode for full integration testing.

Options:

  • --disable-sharing: Creates opencode.json with sharing disabled
  • --keep: Don't clean up sandbox on exit
  • --no-git: Skip git initialization (tests non-git fallback)

Obsidian utility:

./tests/manual/local/fix-vault-links.sh /path/to/vault/plannotator

Adds Obsidian backlinks ([[Plannotator Plans]]) to existing plan files in your vault.

SSH Remote Testing (manual/ssh/)

Tests SSH session detection and port forwarding for remote development scenarios.

cd tests/manual/ssh/
docker-compose up -d
./test-ssh.sh

See manual/ssh/DOCKER_SSH_TEST.md for detailed setup instructions.