Proposal: Improved CSS naming, markup for qUnit.

Proposal: Improved CSS naming, markup for qUnit.


I'm building out a set of qUnit tests at work. So far all is going
well, and the tests have proven valuable. However, I'm having some
integration issues with the way qUnit does its reporting and layout.
The biggest isses I see are:
- The testsuite.css file makes some rather intrusive declarations for
BODY and header tags which can mess up the rest of the page.
- The CSS naming used in the reporting markup is a little too generic.
Names for ID like 'banner' and 'main' may already by used by an
existing page.
- The runTest() method of testrunner.js appends its results to the end
of the BODY tag's children, which renders at the bottom of the page.
If individual tests are at the top (followed by a long page), this can
make it hard to read results.
I'd though about forking off the latest branch and addressing this.
However, if the community is already working on it, I'd be happy to
wait for a later version (or even submit changes).
Or maybe I'm misusing the tool?
BSR