Support updating test durations when running for a single group
See original GitHub issueIt would be useful to add support for calculating test durations while using the parameters --splits
and group
. To clarify, this is currently possible but it runs the full test suite, not just the tests for that particular group. Instead, users can calculate the test_durations for each group and then combine the results.
Happy to send a merge request your way if you think this makes sense!
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Set up an open, closed, or internal test - Play Console Help
Using Play Console, you can test your app with specific groups or open your test to Google Play users ... Can I run...
Read more >Run unit tests with Test Explorer - Visual Studio (Windows)
Learn how to run tests with Test Explorer in Visual Studio. ... Duration, Groups tests by execution time: Fast, Medium, and Slow.
Read more >Test splitting and parallelism - CircleCI
A guide for test splitting and running tests across parallel compute environments to optimize your CircleCI pipelines.
Read more >Automatically apply VM configuration updates in a MIG
This document describes how to automatically apply configuration updates to the virtual machine (VM) instances in a managed instance group (MIG).
Read more >What is A/B Testing? A Practical Guide With Examples | VWO
Requires the test to run for a set period to get correct data from it but can't figure out how close or far...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was done in https://github.com/jerry-git/pytest-split/pull/14
Ok so to summarize:
--store-durations
as a required argument for triggering any caching.test_durations
by default, unless the existing--durations-path
argument is passedI agree we probably don’t need to involve the
.pytest_cache
- I can just put the.test_durations
file in my own.gitignore
and get the same result 🙂Yeah I agree 👍