Tests for non-default configurations

• From: James Graham <james@hoppipolla.co.uk>
• Date: Tue, 8 Nov 2016 10:19:45 +0000
• To: "public-test-infra@w3.org" <public-test-infra@w3.org>
• Cc: Ben Kelly <bkelly@mozilla.com>, Mike West <mkwst@google.com>
• Message-ID: <2ea857ee-6a14-e75b-b938-af70a5333249@hoppipolla.co.uk>

We just had a situation where a gecko contributor wrote some 
web-platform-tests for a feature. So far, so good. However a number of 
these tests depended on disabling mixed content blocking, which is 
possible in Firefox through a pref. AIUI it's also possible in other at 
least some other browsers through a flag.

At the present time I think we will take the opinion that such tests 
relating to features that are not on by default and will not become the 
default in the future are not worth upstreaming, and keep them in a 
mozilla-specific directory. Is this acceptable to everyone or are there 
situations where sharing such tests is valuable? If there are, how do 
you want to communicate the information that a specific setting is 
required?

Received on Tuesday, 8 November 2016 10:20:13 UTC