I feel this is better addressed through simple shell automation, which has probably a dozen different ways to solve for this. Blessing the idea of "just try again" as an actual ExUnit feature implicitly encourages community/developer tolerance of this kind of circumstance when all practical efforts should be made to eliminate it from the code first, wherever the problem actually originates. If those efforts fail, then fall back on surrounding it with retry logic on a case-by-case basis. I would personally discourage use of such a feature if it existed.
Shane Sveller On Monday, October 19, 2020 at 9:30:34 PM UTC-5 [email protected] wrote: > *Problem*: > for heisnbugs and race conditions it is useful to rerun a set of tests a > number of times. > Currently you must alter the suite(s) to wrap the the test(s) in `Enum`s > which is obvioiusly tedious > > *Naive Implementation Proposal*: > Add a `--rerun-count` command line option that would default to 1 but wrap > the test run with `1..<rerun-count> |> Enum( > current_test_runner_parent_function )` > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/3581cdf4-4d23-41d1-afaa-151995e450f8n%40googlegroups.com.
