-
Notifications
You must be signed in to change notification settings - Fork 3
run playgrounds in playwright #536
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
base: develop
Are you sure you want to change the base?
Conversation
- testType: connect | ||
configFile: playwright.config.connect.ts | ||
env: | ||
PLAYWRIGHT_NUM_CORES: 4 |
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.
do we have to list all ENVs here explicitly?
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.
An alternative is to save all env vars into one github secret, and then to print it in its entirety into an env file in the github runner before running the tests. This way we wouldn't have to modify the workflow file whenever we add or remove a test env var, but I think our current approach is better because it is easier to modify the value of each individual environment variable in github secrets
…e every test group
No description provided.