You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What other testing is required beyond this for both the HATF Web Media API and the User Agent specifications?
Or do we take the "walk before we run" approach and just get the W3C tests in place and working for the first version. Then add to this later as the WAVE project progresses?
The text was updated successfully, but these errors were encountered:
I think there is also the issue of any areas of the published Web Media API spec that are not covered by exisiting W3C tests. Regardless, I agree the latter is the best approach. I've updated the "Phase 1, 2 & 3" in the Test Approach document to propose this (i.e. for HATF testing: Phase 1 - get the W3C tests running. Phase 2 - plug any gaps that can be filled with currently available non-W3C test materials. Phase 3 - WAVE writes bespoke tests to plug any remaining gaps, if any).
Current approach is to take a subset of the W3C web platform tests https://github.com/w3c/web-platform-tests/ .
What other testing is required beyond this for both the HATF Web Media API and the User Agent specifications?
Or do we take the "walk before we run" approach and just get the W3C tests in place and working for the first version. Then add to this later as the WAVE project progresses?
The text was updated successfully, but these errors were encountered: