vscode/test
Benjamin Pasero 2ddc1e4fc5
Produce logs during test runs (integration, smoke) and publish as artefacts (#126065)
* first cut upload log files from integration test runs

* always publish log files

* move logs into integration-tests folder

* also produce logs for smoke tests

* store remote log files

* wire in logspath arg properly

* always publish logs

* enable logs for browser based smoke tests

* log only in verbose
2021-06-15 08:33:26 +02:00
..
automation Produce logs during test runs (integration, smoke) and publish as artefacts (#126065) 2021-06-15 08:33:26 +02:00
integration Produce logs during test runs (integration, smoke) and publish as artefacts (#126065) 2021-06-15 08:33:26 +02:00
leaks add leak test scaffolding 2021-05-06 14:45:12 +02:00
monaco Switch to deepStrictEqual part of #118667 2021-03-30 12:05:06 -04:00
smoke enable smoketest on linux 2021-06-11 12:19:17 +02:00
unit Updates sinon from 1.17 to 11.1. 2021-06-09 10:03:46 +02:00
.mocharc.json eng: update mocha 2 -> 8 2020-12-17 11:24:15 -08:00
cgmanifest.json
README.md Web: run integration tests as part of our product builds (fix #83923) 2020-02-10 11:23:00 +01:00

VSCode Tests

Contents

This folder contains the various test runners for VSCode. 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)
  • ui: our suite of manual UI tests