[HTTPS-Everywhere] Recommendations for testing only changed rules

[Nick Semenkovich]

Hm, this does look a bit tricky.

I *think* there's a snippet in FB React that does this, first by cloning
the repo (to a maxdepth of 50):

https://travis-ci.org/facebook/react/jobs/44626578

On Thu, Feb 26, 2015 at 1:46 PM, Jacob Hoffman-Andrews <jsha at eff.org> wrote:

> Hi all,
>
> Right now our automated ruleset test on Travis only tests that updated
> rulesets have sufficient test coverage. Ideally I'd like it to also run
> a fetch test to make sure all domains exist, answer on 443, and provide
> a success response (and eventually, test for mixed content).
>
> However, running a fetch test for all rulesets on all pull requests
> would take too long. So I'd like to make pull requests on Travis test
> only the rules changed in that pull request. Has anyone done this? Any
> suggestions?
>
> One confounding factor: Travis does a shallow clone, so it's not trivial
> to do a diff --name-only against origin/master. I've tried adding a
> fetch command to the test, but no luck so far.
>
>
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere
>



-- 
Nick Semenkovich
Laboratory of Dr. Jeffrey I. Gordon
Medical Scientist Training Program
School of Medicine
Washington University in St. Louis
https://nick.semenkovich.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20150302/9659bd0a/attachment.html>