code-server/test
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
..
browser/pages feat: add custom codecov 2021-06-28 11:41:48 -07:00
e2e Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
unit Move onLine to utilities 2021-06-29 12:04:31 -05:00
utils Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
package.json chore: upgrade to Playwright 1.12 with its new test-runner 2021-06-10 15:09:38 +02:00
playwright.config.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
tsconfig.json refactor: move jest around and add code coverage 2021-01-22 14:18:45 -07:00
yarn.lock chore: upgrade to Playwright 1.12 with its new test-runner 2021-06-10 15:09:38 +02:00