On 2017-03-20 2:19 PM, Anne van Kesteren wrote: > web-platform-tests has a nice feature which generates a bunch of > boilerplate for you for dedicated worker tests and tests that can be > run both in a window and a dedicated worker: > > http://web-platform-tests.org/writing-tests/testharness.html > > (Soon we'll also have it for just window tests, so you don't have to > copy-and-paste the HTML-specific bits of tests anymore.) > > Now this `.any.js` convention might be extended to also generate tests > for shared and service workers. > > We've had some requests to start using this for features that are > available in these various contexts. However, that does mean we'd up > to quadruple the number of tests (for Fetch, WebSocket, File API, > Encoding, HTTP cache, etc.). > > Aside from letting you all know this feature exists and is awesome, > I'd also like to know if we should put any restraints on ourselves > when applying it.
I think running these tests is a good idea, these help catch edge case bugs where for example some pointer is null for a worker and we either forget to check it or do check it and end up having a slightly incorrect behavior as a result... I expect those types of issues to creep in over time if we don't have some already. _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
