Unit and acceptance testing strategy?
Thank you for the excellent work on the H5P tooling -- it's exciting to see a new take on educational content.
From the perspective of a developer and prospective adopter of H5P, I'd like to see some degree of automated testing around the authoring tool, integration plugins and the various content types. I noticed that testing doesn't appear on the H5P roadmap and am curious as to the stance on testing in the developer community.
If tests were provided, would they be likely to be accepted?