Files
vscode/test
57be0b4bb3 test: add UI validation evidence capture (#330338)
* feat: add UI validation evidence capture

Add isolated scenario runs with step overlays, screenshots, multi-page video, traces, HTML reports, and CDP inspection for embedded editor surfaces.

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

* fix: harden UI evidence lifecycle

Roll back failed starts, support recursive settings, derive failed outcomes, handle application close races, and clean up detached CDP sessions.

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

* fix: address follow-up UI evidence review

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

* fix: serialize UI evidence operations

Reserve evidence lifecycle transitions, recover open windows, validate report links and profile arguments, and observe CDP commands without promise races.

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

* fix: serialize MCP application creation

Reserve in-flight application creation synchronously, share only compatible launches, and make stop wait for startup to settle.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485

* fix: avoid evidence cleanup deadlock

Stop only the evidence-owned application during finalization so a queued launch waiting for profile cleanup cannot form a promise cycle.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
2026-08-12 18:32:40 +00: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)