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

[Feature Request] Optimizing functional test time with pytest-testmon #416

Closed
xianyuanliu opened this issue Oct 16, 2023 · 1 comment · Fixed by #427 · May be fixed by #413
Closed

[Feature Request] Optimizing functional test time with pytest-testmon #416

xianyuanliu opened this issue Oct 16, 2023 · 1 comment · Fixed by #427 · May be fixed by #413
Assignees

Comments

@xianyuanliu
Copy link
Member

xianyuanliu commented Oct 16, 2023

🚀 Feature Request

I'm looking to use Pytest-testmon to optimize test execution time in the GitHub Action. I use the GitHub Action Cache to manage .testmondata storage and restoration. Here's my design approach:

  1. The main branch undergoes scheduled tests to generate a new .testmondata.
  2. Branches within PRs simply restore the generated .testmondata for a faster test, without updating it.

Motivation

Is your feature request related to a problem? Please describe.
Nope.

Pitch

Describe the solution you'd like
Using pytest-testmon to test the changed codes only.

  1. However, an issue arises when I execute pytest --testmon-nocollect within the PR: a new .testmondata is unexpectedly generated in the GitHub Action Cache. I'm unsure about the root cause of this.

  2. Please note that pytest-testmon might not be compatible with codecov. (See Ref. link1, Ref. link2 and Ref. link3)

Are you willing to open a pull request? (We LOVE contributions!!!)
#413

@xianyuanliu xianyuanliu changed the title Decrease the functional testing time [Feature Request] Optimizing functional test time with pytest-testmon Oct 16, 2023
Copy link
Contributor

This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants