i want to set up a way to see which parts of the code are not covered by any unit tests, and which parts do not comply with a basic style guide we can define.
i am experimenting with qunit+blanket in the ‘qunit’ branch, and will see if i can get the wireclient covered with that.
i searched for alternative frameworks, and i think qunit+blanket is the easiest set up to get started with.
teste is probably hard for new contributors to get familiar with, and mocha and jasmine seem to be equivalent to qunit but not as super-simple to get started with.
doing this means we will have some duplication between our existing teste suites and the new qunit tests, but i guess that’s inevitable unless we want to stay with teste for all our testing.
at this point it seems teste doesn’t support visualization of coverage, and it seems to me using a test framework that nobody else uses is an unnecessary risk.
i want to increase the number of tests anyway, so i think now would be a good time to switch from teste to qunit+blanket. counter-proposals welcome