For those that would rather it be opt-out, remember that we can always make
it opt-out later, once we have more experience with the feature.
Regarding the suggestion to have `--random 0` mean not to use randomizing,
I also think that could be confusing. 0 is also a valid integer seed, and
it se
> I usually agree with new features being opt-in, but perhaps this case is
> different?
>
> If I had tests that are breaking if executed randomly, I’d want to know
> about it yesterday. IOW, I’m having difficulty imagining a scenario where
> the user would be thankful for not activating this f
> On 10.03.2021., at 13:06, Mariusz Felisiak wrote:
>
>> I suggest we add the flag as "--random" taking an integer that is the seed,
>> or 0 to disable.
>
> This kind of APIs are always confusing. Moreover I don't think that changing
> the current behavior is a good idea, it should be opt-in n
Hi,
I agree that it would be a nice new feature.
*I suggest we add the flag as "--random" taking an integer that is the
> seed, or 0 to disable.*
>
This kind of APIs are always confusing. Moreover I don't think that
changing the current behavior is a good idea, it should be opt-in not
op
This would be something I'd really like to see. Also it would be nice to
make it the default.
I suggest we add the flag as "--random" taking an integer that is the seed,
or 0 to disable.
Do check out my project pytest-randomly for a battle-tested project
randomly shuffling tests.
One thing pytes
I'd like to ask folks if they would support reopening ticket #24522, which
is to add a --random option to Django's test runner:
https://code.djangoproject.com/ticket/24522
It was opened 6 years ago and closed as won't fix.
I've been doing some simplifications of the test-suite related code in
Dja
