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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃殌 Feature: parallel test prioritization #5101

Closed
3 tasks done
triwav opened this issue Feb 26, 2024 · 1 comment
Closed
3 tasks done

馃殌 Feature: parallel test prioritization #5101

triwav opened this issue Feb 26, 2024 · 1 comment
Labels
duplicate been there, done that, got the t-shirt...

Comments

@triwav
Copy link

triwav commented Feb 26, 2024

Feature Request Checklist

Overview

I use mocha for automation testing on Roku devices. I've just started working on using parallel to improve the speed of tests. The issue I'm running into is that since you can not specify the order that files are executed in, it is choosing to do the file with the most tests last which then means all the other tests running parallel and then it gets to the final file that takes way longer and the other Roku devices are now just waiting for the final file of tests to run.

Suggested Solution

If there was some way to give prioritization or ordering of tests then test times could be improved in some cases dramatically

Alternatives

I could split the tests into either their own file or in smaller sets of files but then this hurts the organization of tests with describes
I could run the file with the most tests as its own separate command but then any reporting would have to be combined for the final result

Additional Info

I checked the I want to provide a PR to resolve this and would happy to help but would likely need some pointers of where to get going.

@triwav triwav added status: in triage a maintainer should (re-)triage (review) this issue type: feature enhancement proposal labels Feb 26, 2024
@JoshuaKGoldberg
Copy link
Member

I think we can treat this a duplicate of #4322 (a subset). Let's discuss over there. Thanks for filing!

@JoshuaKGoldberg JoshuaKGoldberg closed this as not planned Won't fix, can't repro, duplicate, stale Jul 2, 2024
@JoshuaKGoldberg JoshuaKGoldberg added duplicate been there, done that, got the t-shirt... and removed type: feature enhancement proposal status: in triage a maintainer should (re-)triage (review) this issue labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate been there, done that, got the t-shirt...
Projects
None yet
Development

No branches or pull requests

2 participants