-
Notifications
You must be signed in to change notification settings - Fork 5.9k
feat(testing): add playwright #2643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
4a50ddc
to
98da30c
Compare
98da30c
to
96add41
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks alright to me! Haven't worked much on testing so far - so you might want a second opinion.
96add41
to
2b7dfa4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is quite exciting. 😄
Re-running tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! :)
e6cbf0e
to
6685a3e
Compare
I made your changes and Anmol approved!
This PR adds playwright for end-to-end testing. In ci, we now download the code-server artifact, run code-server in ci and then run tests against it.
Changes
playwright
to/test/package.json
ci.yml
test
job to work withe2e
Additional Notes
Right now,
yarn test
runs both the unit and the e2e tests. This means it will fail locally if you do not havecode-server
running. In the future, we should consider separating the tests. We could havetest:unit
andtest:e2e
and then have separate jobs for each in ci.Follow-up issue: #2646
Todos
pkill node
in ci job