W3C home > Mailing lists > Public > public-test-infra@w3.org > October to December 2016

Re: Stability testing of PRs

From: James Graham <james@hoppipolla.co.uk>
Date: Tue, 18 Oct 2016 13:09:54 +0100
To: Philip J├Ągenstedt <foolip@google.com>, "public-test-infra@w3.org" <public-test-infra@w3.org>
Cc: Rick Byers <rbyers@google.com>
Message-ID: <93eb0fe8-3f74-f81c-a16f-cd4eb51d25e4@hoppipolla.co.uk>
On 18/10/16 13:03, Philip J├Ągenstedt wrote:
> That sounds fantastic, James!
>
> If you've modified a common.js but no tests, will there be a way to
> manually trigger a run for the tests you happen to know are affected?

I don't know of an easy way to provide input to travis other than the 
source tree. One could imagine an optional map of support files to 
tests, and some tooling to help generate it for simple cases, I suppose.

> Using the same infrastructure, would it be possible to paste the test
> results into a comment in the PR after every change?

Yes.
Received on Tuesday, 18 October 2016 12:10:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:12 UTC