Skip to content
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

[CT-1579] Split integration tests into groups #6354

Closed
Tracked by #6798
MichelleArk opened this issue Dec 1, 2022 · 2 comments · Fixed by #6346
Closed
Tracked by #6798

[CT-1579] Split integration tests into groups #6354

MichelleArk opened this issue Dec 1, 2022 · 2 comments · Fixed by #6346
Assignees
Labels
enhancement New feature or request

Comments

@MichelleArk
Copy link
Contributor

MichelleArk commented Dec 1, 2022

We can use the pytest-split pytest plugin (or an alternative?) to split long-running integration test suites into groups and run the groups in parallel to speed up CI times.

Draft example for how this could look: #6346

Considerations

  • Discovered some flaky tests that had dependencies on other tests for their success in the draft. We should aim to detect resolve as many of these as possible prior to introducing test groups else more flakiness may be discovered in unrelated PRs.
  • More GHA tasks => more email clutter when things fail
  • Integration test results are currently uploaded in a unified (all tests for python-version/os) form at the end of the workflow. How is this data used? Is it feasible to stitch together separate artifacts (one per python-version/os/group) into a unified view? using dbt??
@MichelleArk MichelleArk added the enhancement New feature or request label Dec 1, 2022
@MichelleArk MichelleArk self-assigned this Dec 1, 2022
@github-actions github-actions bot changed the title Split integration tests into groups [CT-1579] Split integration tests into groups Dec 1, 2022
@dbeatty10
Copy link
Contributor

➕ Speeding up CI times would be awesome!

@github-actions
Copy link
Contributor

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

@github-actions github-actions bot added the stale Issues that have gone stale label May 31, 2023
@emmyoop emmyoop removed the stale Issues that have gone stale label Jun 6, 2023
@emmyoop emmyoop mentioned this issue Jul 26, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants