Following the summary of what we achieved in wpt in the last year, I'd
like to solicit input from the gecko community to inform the
priorities of various pieces of wpt work for the next year.
In order to maximise the compatibility benefit we have two long term
objectives for the web-platform-tests work at Mozilla:
* Make writing writing web-platform-tests the default for all
web-exposed features, so that we only write unshared tests in
exceptional cases (e.g. where there is a need to poke at Gecko
internals).
* Ensure that gecko developers are using the web-platform-tests
results to avoid interoperability issues in the features they
develop.
Obviously we are some way from achieving those goals. I have a large
list of things that I think will make a difference, but obviously I
have a different perspective to gecko developers, so getting some
feedback on the priorities that you have would be good (I know I have
already have conversations with several people, but it seems good to
open up the question to a broader audience). In particular
it would help to hear about things that you would consider blockers to
removing tests from non-wpt suites that are duplicated in wpt
(assuming exact duplication), and limitations either in the
capabilities of wpt or in the workflow that lead to you writing other
test types for cross-browser features.
Thanks
(Note: I set the reply-to for the email version of this message to be
off-list as an experiment to see if that avoids the anchoring effect
where early replies set the direction of all subsequent discussion. But
I'm very happy to have an on-list conversation about anything that you
feel merits a broader audience).
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
