QUnit Plugins (or "Setup Step") in CLI

[trentmwillis]

On the QUnit website we have a list of plugins that are easy to use in the browser; you simply load an additional asset which then configures QUnit. Now that we have a CLI, we should have a prescribed approach for enabling plugins/API extensions in Node.

I have some ideas on how to approach this and will come back to document them later, but I wanted to open this issue now as a reminder and in case anyone else has thoughts/ideas on how to approach this.

[rwjblue]

@trentmwillis - I am curious on what your ideas are here. I'm keen to have this functionality as well, and I also would like to ensure that I can bake whatever discovery mechanism you settle on into ember-qunit...

[trentmwillis]

Finally circling back to this. I think having a --require option from the CLI is a good first step for this. However, I would like to have two further features supported:

• A .qunitrc (name TBD) config file that allows users to define options that are then used by the CLI without having to be manually entered
• (Maybe) An auto-discovery mechanism whereby we automatically --require packages that have qunit-plugin or some other predetermined keyword in their package.json

[john-kurkowski]

Would love a .qunitrc. There are QUnit.config options that the CLI currently doesn't let me supply, like hidepassed.