We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please provide details about:
What you're trying to do
Follow up to RFC: Parallelizing across machines in CI #1811. Better load balance test files across multiple CI machines
Why you can't use AVA for this
Ava sorts files by file name, which is not the best load balancing strategy, especially when some tests are slower than others.
And maybe how you think AVA could handle this
Allow setting a custom comparator to be used here:
ava/lib/api.js
Line 180 in 3131ccd
Alternatives: Ensure number of tests per file is low enough via a lint rule.
More context: netlify/cli#4178
The text was updated successfully, but these errors were encountered:
What would you think about being able to configure the comparator function in an ava.config.js file?
ava.config.js
Sorry, something went wrong.
That would be great and will solve our use case 💯
Are you open for me to contribute this change or prefer someone else to do it?
All yours @erezrokah! Let me know if you have questions.
erezrokah
Successfully merging a pull request may close this issue.
Please provide details about:
What you're trying to do
Follow up to RFC: Parallelizing across machines in CI #1811. Better load balance test files across multiple CI machines
Why you can't use AVA for this
Ava sorts files by file name, which is not the best load balancing strategy, especially when some tests are slower than others.
And maybe how you think AVA could handle this
Allow setting a custom comparator to be used here:
ava/lib/api.js
Line 180 in 3131ccd
Alternatives:
Ensure number of tests per file is low enough via a lint rule.
More context:
netlify/cli#4178
The text was updated successfully, but these errors were encountered: