In general +1, sounds good. I have two questions regarding this proposal:
- I have the fear that the approach of just calling all kinds of documents won’t lead to a complete validation as it might miss many dialogs etc. that are only accessible by clicking on certain elements. Would it be possible to additionally integrate this testing into the existing Selenium-based integration tests we have? Either transparently (by validating after every page load or even after every click when enabled) or also just explicitly that integration tests would explicitly call the validator at certain points in the test? Or alternatively/additionally, could we integrate this in page tests where we have just some HTML fragments usually?
- Do you have any plan how we deal with the initial phase where the validator will find a lot of problems? Do we just ignore the test failure? What’s the output of the validator, can we use it to measure progress?