Re: https/wss testing in web-platform-tests

I would guess you overestimate the barrier both of these would
present.  If you're installing wptserve as a developer, pulling
openssl as another dependency is pretty low friction - many will have
it already.

As far as installing the certificate into your browser - that only
matters if you want to run the https tests.  There should be no action
required to simply start a wptserve instance that also listens on
https with a locally-generated certificate.

On Mon, Oct 13, 2014 at 10:35 AM, James Graham <james@hoppipolla.co.uk> wrote:
> On 13/10/14 18:20, Brad Hill wrote:
>> Why would we not just always require an https endpoint to be running
>> if we're going to automatically generate a test certificate, anyway?
>> Why put the burden on test authors to mark every test that requires
>> https?
>
> I had assumed that it wasn't a good idea because a) it requires people
> to have openssl installed to generate the CA and host cert/keys, b)
> actually trusting the cert only works well with wptrunner since you
> don't want to trust the fake CA into your real browser profile (or run
> your normal browser in a special don't-check-certs mode) c) we don't
> necessarily have a code path to install the CA cert in all browsers.
>
> If I am overestimating the importance of these, that would be great to
> know, because I agree that putting any burden on test authors here sucks.
>