Capture Files changed page fixtures #2

Parent

#1

What to build

A set of sanitized fixtures of GitHub's current Files changed page that the end-to-end tests serve in place of github.com. Signed-out visitors get the classic page, so a person with a GitHub session must capture them.

Create a demo pull request that mirrors the design prototype's demo (22 files: tests, lockfiles, generated files, docs, a renamed file, a deleted file, and a review comment on a test file), then save the pages and the responses that the tests need to replay a real review session.

Acceptance criteria

• A demo pull request mirrors the prototype's 22 files and adds a renamed file, a deleted file, a path that contains a space, and a review comment on a test file.
• Fixtures exist for the Files changed page of the demo pull request, a single-commit view, a commit-range view, the classic Files changed page, a large pull request in single file mode, and a pull request large enough to load files incrementally or virtualize the diff.
• The fixtures include the responses that GitHub loads after the first render (more files, route changes), so the tests can replay them.
• Personal data, tokens, and session values are removed from every fixture.
• A short note explains how to refresh the fixtures and records whether the sidebar tree lists every file before all diff blocks load.

Blocked by

None — can start immediately.