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
..
audit.sh	feat(ci): add audit job for security	2021-04-06 11:06:04 -07:00
ci.sh	feat(ci): add audit job for security	2021-04-06 11:06:04 -07:00
fmt.sh	chore(deps-dev): bump prettier-plugin-sh from 0.6.1 to 0.7.1 (#3680)	2021-06-28 22:06:55 +05:30
gen_icons.sh	chore(deps-dev): bump prettier-plugin-sh from 0.6.1 to 0.7.1 (#3680)	2021-06-28 22:06:55 +05:30
lint.sh	chore(deps-dev): bump prettier-plugin-sh from 0.6.1 to 0.7.1 (#3680)	2021-06-28 22:06:55 +05:30
postinstall.sh	refactor: move jest around and add code coverage	2021-01-22 14:18:45 -07:00
test-e2e.sh	Spawn a code-server instance for each test suite	2021-06-29 12:06:38 -05:00
test-unit.sh	refactor: add scripts to separate unit, e2e tests	2021-03-12 12:00:56 -07:00
update-vscode.sh	chore(deps-dev): bump prettier-plugin-sh from 0.6.1 to 0.7.1 (#3680)	2021-06-28 22:06:55 +05:30
watch.ts	Move onLine to utilities	2021-06-29 12:04:31 -05:00