Files
vscode/test
57ca46fc0d Render evidence chapters from the automation harness (#331574)
* Render evidence chapters from the automation harness

Record when video recording starts so captured step timestamps can be expressed as offsets into the recording, and add a script that composes step chapter cards onto a finished run. This lets a clean capture be annotated afterwards instead of drawing a banner into the window under test, and gives local runs and CI one shared implementation.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485

* Write the chapter renderer in TypeScript

Hygiene rejects new JavaScript files, so move the renderer into the compiled MCP sources and invoke it from out/ instead of adding an eslint-allowed-javascript-files exception.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485

* Address review of evidence chaptering

Sample the recording origin at page creation instead of context or application creation, state the residual imprecision in the contract, render manifest text literally, point the report at the annotated recording, and refuse multi-window runs rather than chaptering onto only the first recording.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
2026-08-19 10:13:42 -07:00
..
2026-08-07 12:01:10 +08:00

VS Code Tests

Contents

This folder contains the various test runners for VS Code. Please refer to the documentation within for how to run them:

  • unit: our suite of unit tests (README)
  • integration: our suite of API tests (README)
  • smoke: our suite of automated UI tests (README)
  • sanity: release sanity tests (README)