On 08/03/2019 15:06, Boris Zbarsky wrote:
On 3/7/19 7:31 PM, Ehsan Akhgari wrote:
*web-platform-tests*: This is an intervention which different engines do
not agree on yet. Creating a web-platform-test for it would be very
simple
but it will be failing in the engines that do not agree with the
intervention. I'm not sure what the recommendation for testing these
types
of changes is, would be happy to submit a test if there is a path for
getting them accepted into wpt.
Other vendors have been landing tests with ".tentative" as the last part
of the filename before the suffixes the test harness expects (so e.g.
"web-locks/mode-shared.tentative.https.any.js").
I think doing that here is fine; we may want the tests or the commit
message involved to point to an explainer or something tracking the need
for a spec change or something like that...
Yes, this seems correct to me too; a .tentative. test is the right way
to land a test for something that isn't yet standardised, and it should
somehow link to the relevant discussion but there isn't an explicit
convention for how that should happen (commit message vs comment vs link
element, for example). See the end of [1] for the documentation.
[1] https://web-platform-tests.org/writing-tests/file-names.html
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
