We'd like to use a tool like Axe to help lockdown WCAG rules for accessibility, but the QUnit page itself has some violations that we are forced to filter out. Ideally, yes, tests would only attempt to lockdown their particular widget/section, likely placed in the qunit-fixture

There is a getting started guide that covers the basics for the Node and Browser use cases.

In qunitjs/qunitjs.com@0a70d75, I've added a dedicated page for the QUnit CLI with Node.

This ticket is to create a similar page for the Browser runner as well.

It could cover:

• How to include qunit.js from node_modules (ref https://git

module('A', function() {
  module('foo', projectsFiltersSetup);
});

module('B', function() {
  module('foo', auditsFiltersSetup);
});

Module name is used on line 2. eslint(qunit/no-identical-names)