-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Run unit and e2e tests in parallel #19161
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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.
Pull Request Overview
This PR updates the CI configuration to run unit and end-to-end tests in parallel by introducing a strategy matrix in the workflow. Key changes include:
- Adding a matrix strategy with a test_type parameter to distinguish unit and e2e jobs.
- Appending the matrix test type to environment variables and artifact names.
- Adjusting job conditions accordingly and updating the master workflow to trigger on pull requests to master.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
File | Description |
---|---|
.github/workflows/test-target.yml | Added a strategy matrix and modified steps to run tests in parallel. |
.github/workflows/master.yml | Added pull_request trigger on master to support the new testing flow. |
Comments suppressed due to low confidence (2)
.github/workflows/master.yml:7
- Confirm that adding a pull_request trigger for the master branch is intentional, as this change may lead to additional workflow runs which could affect CI utilization.
pull_request:
.github/workflows/test-target.yml:96
- Ensure that both unit and e2e tests have appropriate test coverage and that downstream steps correctly aggregate their respective artifacts based on the matrix test type.
matrix:
test_type: ['unit', 'e2e']
WIP
What does this PR do?
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged