+8 Yiming Chen wrote:
> Before proposing more API options, let me first try to hack a working
> version of case-level async ExUnit.
> So that I can benchmark the performance differences between case-level and
> module-level async runner.
> And we can then decide if it's worth purs
Before proposing more API options, let me first try to hack a working
version of case-level async ExUnit.
So that I can benchmark the performance differences between case-level and
module-level async runner.
And we can then decide if it's worth pursuing case-level async further.
Best,
Yiming
On
Sorry for the late response.
I'll look into the API options again and post the results here.
On Tuesday, September 5, 2023 at 1:21:01 AM UTC+8 José Valim wrote:
> If we want to add more parallelism later, then it is worth discussing
> future developments of the API now, so we don't put
the
> worst case scenario we will run M * T processes at once (M = Modules, T =
> Tests). We could try to introduce coordination between M * T to adhere to a
> limit of max_cases, but that will likely be too complex.
>
>
> On Mon, Sep 4, 2023 at 2:53 PM Yiming Chen wrote:
>
it is desirable and it has come up in the past:
> https://github.com/elixir-lang/elixir/pull/11949#issuecomment-1177262901
>
> Although I think async: :per_module is what most people want, since the
> tests in the same module tend to access the same resource, opting-in for it
> to
Currently, ExUnit's `async: true` option would run test cases in this
module synchronously,
but only run this module asynchronously along with other `async: true`
modules.
This is to propose we add an option for ExUnit to run asynchronously by
test cases.
# Background
1. Async by module was a
