Our
goal is not "decent" but complete HTML5 compatibility.
The
target is that our HTML output is to be validated by HTML5
validators with no errors shown. We already selected the
industry-standard HTML5 validators to verify this.
Specifically,
we are using in development
http://validator.w3.org/
through a browser extension. This MUST be automated at a
certain point.
What
I'm trying to avoid here is coding specifically for a target
browser or platform. I suggest to not restrict testing to a
certain browser/platform/version, but use what ever the tester
uses in real life.
In
case of presentation bugs are discovered, first we have to
rule out an issue with the browser of choice by testing visual
reproducibility with another browser on the same page and
verifying browser's HTML5 compatibility.
For
visual reference, widgets in the page change across different
platforms and browsers. Do we have test cases for the
appearance ?
The
test cases should not be dependent or executed with a
specified platform/browser version.
Cheers,
Alex