Closed
Description
After hours of debugging and a false positive with a dependabot PR, we've come to the conclusion that we should have testing in place for our dev workflow: yarn watch
.
This will prevent issues like #2962 from happening again.
One way to achieve this is by:
- adding a new script called
yarn test:watch
which is similar toyarn test:e2e
- add new CI step/job for running the e2e tests against code-server running with
yarn watch
We'd have to add some timeout or sleep though since running with yarn watch
takes time to finish.
Related: