Repository navigation
test_runner: warn if only is used without properly enabling only tests #46448
Description
Activity
@cjihrig I can take a look at this one, if nobody else has picked it up.
- Should this warning be a test diagnostic? or use a different mechanism for warnings?
- Would this be emitted once per parent test, once per test file or something different?
@cjihrig I can take a look at this one, if nobody else has picked it up.
- Should this warning be a test diagnostic? or use a different mechanism for warnings?
- Would this be emitted once per parent test, once per test file or something different?
I think either
process.emitWarning, or simplytest.diagnosticsis okReacted by Richie McCollI think we should prefer a test diagnostic.
Reacted by Moshe Atlow and Richie McColl- added a commit that references this issue
on Feb 21, 2023 - added 2 commits that reference this issue
on Mar 3, 2023 - added 2 commits that reference this issue
on Mar 13, 2023
What is the problem this feature will solve?
onlytests require enabling only mode, otherwiseonlydoes nothing. This can lead people to think thatonlydoes not work.What is the feature you are proposing to solve the problem?
The test runner should warn if someone tries to use
onlywithout properly enabling it.What alternatives have you considered?
Doing nothing.