Skip to content

Conversation

@aehnh
Copy link

@aehnh aehnh commented Jun 10, 2025

No description provided.

@aehnh aehnh self-assigned this Jun 10, 2025
@aehnh aehnh closed this Jun 10, 2025
@aehnh aehnh reopened this Jun 10, 2025
- testType: connect
configFile: playwright.config.connect.ts
env:
PLAYWRIGHT_NUM_CORES: 4
Copy link
Contributor

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?

Copy link
Author

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

@aehnh aehnh requested a review from incorbador June 24, 2025 15:50
@incorbador incorbador merged commit 2739347 into develop Aug 8, 2025
3 checks passed
@incorbador incorbador deleted the webserver branch August 8, 2025 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants