We just restored the existing vows test suite.

But I don't think we should add new tests to it (or only in a limited manner).

• there are many tests with multiple assertions, first failing hides other potential failling ones
• vows is another abandoned test framework
• generating those kind of repetitive tests is more verbose then in current frameworks (like jest)

I think this is again a high prio issue since it lower the barrier to contribution and we will hopefully add a lot of tests for all the known issues. (I imagine to add branches or even draft PRs with a failing test case as a first step of every investigation.)

Suggested LOD(level of done):

• decide for a test framework that is maintained and well known to make contributions easy: we decided using jest, it landed with test: Add jest and first tests #114
• add a first (green, but make sure it can fail) test to the repo including CI on github actions => also part of test: Add jest and first tests #114
• propose a concept how to structure the tests in a consistent manner (e.g. a folder per module, test suite per function or "topic"), see
  • Improve test coverage with future-proof testing strategy #72 (comment)
  • Improve test coverage with future-proof testing strategy #72 (comment)
  • document and apply the proposal once it's agreed upon
• cover more parts of the DOM API:
  • setAttributeNode and setAttributeNodeNS
• Improve Stryker score

@ owners & authors Please keep this description up to date with results from the discussion below.