-
Notifications
You must be signed in to change notification settings - Fork 16
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
migrate integration tests to playwright #650
Conversation
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.
Nice! looking great, nice to see that net-negative in code :)
If it's working locally, but not in CI, I think you'll need to tweak the github actions file, we figured how how to run those tests in LLR if you need a reference
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.
Really nice job. I made a few edits:
- rewrote the directly structure from
frontend/integration
tointegration
, since they're really two separate things - update docs, specifically the
integration tests
portion - used built-in fixture from pytest-playwright for setting up the playwright browser
@munnsmunns please merge if you're ok w/ my revisions! |
scratch that; broken in CI.... let me take a look |
ok, I think it's fixed, ok to merge @munnsmunns if you're happy... |
Implement Playwright as our engine for integration tests, replacing selenium/helium. This will make it easier to write future tests, and it runs our current tests slightly faster than before.
Also adds the command
make test-integration-debug
, which runs the integration tests in headed mode with a chrome window and a debugger.Performance impacts, around 70s vs 130s w/ selenium:
old:

new:
|