vscode/test
Connor Peet 0899758dae
ipc: use vql for uint types (#167407)
* ipc: use vql for uint types

On the plane I was reverse-engineering ipc.ts to implement it in Rust
and see if we could have a "service mode" for the CLI that we could
interact with like any other vscode process.

In doing so, I noticed that numbers in the protocol--which are used at
least twice in the message header and ID--were encoded as JSON. I was
curious what benefits we'd get from encoding them as variable-length
integers instead.

It makes the message shorter, as expected. Encode/decode time are very,
very slightly lower. I'm not sure it's worth the extra complexity, but
I have included it here for your consideration.

* fixup tests
2022-12-02 15:54:36 -08:00
..
automation Test - update minimatch (#167101) 2022-11-23 21:33:27 +00:00
integration Test - update minimatch (#167101) 2022-11-23 21:33:27 +00:00
leaks add leak test scaffolding 2021-05-06 14:45:12 +02:00
monaco Re-enable running our eslint rules using ts-node (#159495) 2022-08-30 08:40:04 +02:00
smoke Test - update minimatch (#167101) 2022-11-23 21:33:27 +00:00
unit ipc: use vql for uint types (#167407) 2022-12-02 15:54:36 -08:00
.mocharc.json eng: update mocha 2 -> 8 2020-12-17 11:24:15 -08:00
cgmanifest.json rename isOnlyDevelopmentDependency to developmentDependency 2018-11-21 16:17:52 +01:00
README.md Cleanup package.json test scripts (#141210) 2022-01-22 13:07:14 +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)