a
/
code-server
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
code-server/test/e2e
History
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
..
models Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
baseFixture.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
browser.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
codeServer.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
globalSetup.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
login.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
logout.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
openHelpAbout.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00
terminal.test.ts Spawn a code-server instance for each test suite 2021-06-29 12:06:38 -05:00