Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple --reporter options on the CLI #1784

Open
Krinkle opened this issue Jul 21, 2024 · 0 comments
Open

Support multiple --reporter options on the CLI #1784

Krinkle opened this issue Jul 21, 2024 · 0 comments
Labels
Component: CLI Type: Enhancement New idea or feature request.

Comments

@Krinkle
Copy link
Member

Krinkle commented Jul 21, 2024

What are you trying to do?

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.js
QUnit.reporters.perf.init(QUnit);
@Krinkle Krinkle added Type: Enhancement New idea or feature request. Component: CLI labels Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: CLI Type: Enhancement New idea or feature request.
Development

No branches or pull requests

1 participant