You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable the perf reporter, in combination with Node.js inspector hooked up to Chrome devtools, but still have the tap reporter enabled as well to increase confidence and improve visibility into what's happened upto a breakpoint.
What actually happened?
The option currently allows only one value, so if you do try to do this today, the last one will win
$ qunit --reporter tap --reporter perf
Other information
On the web we've always allowed multiple reporters. The new QUnit.config.reporters option is also naturally not limited. And on the web we actually enable two reporters by default (perf and html).
Note that you can work around this today by calling the reporter directly from a setup using the --require CLI option
qunit --require ./test/setup.js
// test/setup.jsQUnit.reporters.perf.init(QUnit);
The text was updated successfully, but these errors were encountered:
What are you trying to do?
Enable the
perf
reporter, in combination with Node.js inspector hooked up to Chrome devtools, but still have thetap
reporter enabled as well to increase confidence and improve visibility into what's happened upto a breakpoint.What actually happened?
The option currently allows only one value, so if you do try to do this today, the last one will win
Other information
On the web we've always allowed multiple reporters. The new
QUnit.config.reporters
option is also naturally not limited. And on the web we actually enable two reporters by default (perf
andhtml
).Note that you can work around this today by calling the reporter directly from a setup using the --require CLI option
The text was updated successfully, but these errors were encountered: