Https-everywhere: Only run ruleset tests for ruleset changes

[Bisaloo]

Type: feature request

Oftentimes, the travis tests fail for something that is totally unrelated to the changes in the PR. This can create confusion for new contributors, especially if they're new to GitHub and continuous integration.

It would be nice to have a way to only run validations, fetch, and preloaded tests when the only changes concern rules.

I don't think this would have any security implications but I need to think about it more.

[pipboy96]

I hope someday repos and the extension code will have separate Git repos. I feel like this is not going to happen any time soon though.

[pipboy96]

I think fetch test is not triggered unless at least one ruleset file had been added or changed.

[Hainish]

@pipboy96 it will be a top priority to separate the extension from the rulesets in the next year or so.

[Hainish]

I think fetch test is not triggered unless at least one ruleset file had been added or changed.

This was definitely true in the past, but appears not to be the case anymore.

https://github.com/EFForg/https-everywhere/blob/master/test/run_travis.sh#L69

Here, ONLY_RULESETS_CHANGED is set but never used. It shouldn't be difficult to auto-pass the non-ruleset tests if only rulesets have been changed.

[pipboy96]

@Hainish Should I make a PR to fix it?

[Hainish]

Thanks, that would be great!