code-server/test/utils
Asher da4de439e0
Spawn a code-server instance for each test suite
This uses the current dev build by default but can be overidden with
CODE_SERVER_TEST_ENTRY (for example to test a release or some other
version).

Each instance has a separate state directory. This should make
parallelization work.

This also means you are no longer required to specify the password and
address yourself (or the extension directory once we add a test
extension). `yarn test:e2e` should just work as-is.

Lastly, it means the tests are no longer subject to yarn watch randomly
restarting.
2021-06-29 12:06:38 -05:00
..
constants.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
cssStub.ts refactor: create test/utils 2021-03-12 12:00:56 -07:00
globalSetup.ts Run each e2e test in a new workspace 2021-06-29 12:03:37 -05:00
helpers.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
httpserver.ts Share common util code with VS Code 2021-05-04 13:29:40 -05:00
integration.ts Use warn log level for integration tests 2021-05-06 14:27:16 -05:00
wtfnode.ts refactor: create test/utils 2021-03-12 12:00:56 -07:00