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.

Sign up for GitHub

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

Jump to bottom

Run just a single testfile to populate caches before testing, not an entire batch #332

Closed
Witiko opened this issue Aug 21, 2023 · 0 comments · Fixed by #334
Closed

Run just a single testfile to populate caches before testing, not an entire batch #332

Witiko opened this issue Aug 21, 2023 · 0 comments · Fixed by #334
Labels
continuous integration Related to the continuous integration speed Related to speed improvements tests Related to the unit testng framework
Milestone
3.0.0

Comments

@Witiko
Copy link
Owner

Witiko commented Aug 21, 2023

With the new unit testing framework added in #316, we run a single batch to populate caches before running the remaining batches in popular. However, this is needlessly costly. Using a single testfile (i.e. a batch of size 1) would achieve the same effect faster.
@Witiko Witiko added tests Related to the unit testng framework speed Related to speed improvements continuous integration Related to the continuous integration labels Aug 21, 2023
@Witiko Witiko added this to the 3.0.0 milestone Aug 21, 2023
@Witiko Witiko mentioned this issue Aug 21, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
continuous integration Related to the continuous integration speed Related to speed improvements tests Related to the unit testng framework
Projects
None yet
Milestone
3.0.0
Development

Successfully merging a pull request may close this issue.

Run just a single testfile to populate caches before testing, not an entire batch Witiko/markdown
1 participant
@Witiko