Closed Krinkle closed 6 days ago
Strawman proposal:
--seed=new
and --seed=true
will no longer be treated as actual seeds but instead as instruction to generate a new seed. I think this will be more intuitive than introducing a separate option like --newseed
, and keeps the diferent interfaces (preconfig, config, URL param, CLI option) more in line with each other.Alternatives I considered:
--newseed
CLI option (along with ?newseed
parameter, and QUnit.config.newseed = true
). This will instruct QUnit to generate a new seed, and assign it to QUnit.config.seed
. This can be backported to QUnit 2.x to ease the transition and allow for forward-compatible adoption.--seed
CLI option to require a value, thus qunit --seed
and qunit --seed -- test/
would fail due to a missing option value.
When using
qunit --seed
it will default to runningtest/**.js
and will print the randomly selected seed for future re-use. This works as expected:The problem is, when using a files argument, the command becomes ambiguous and it naturally becomes the value for the seed instead:
This can be worked around currently by using
--
to mark the end of the options and the start of the arguments: