Feature #11376

Remove @check_tor_leaks tag and always look for leaks

Added by anonym 2016-04-25 06:55:49 . Updated 2019-09-07 06:37:17 .

Status:
Confirmed
Priority:
Normal
Assignee:
anonym
Category:
Test suite
Target version:
Start date:
2016-04-25
Due date:
% Done:

0%

Feature Branch:
Type of work:
Discuss
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The reason I made the Tor check opt-in via the @check_tor_leaks was that I envisioned it later turning in to a @uses_tor tag, that also would deal with scenario re-running on failure and other stuff. It seems clear now that won’t ever happen (instead we seem to go the Feature #9519 way), so I think we should just always run this both to simplify our .feature files, and to make sure we never forget this for new scenarios.

We’ll need a way to opt-out from this though: some scenarios, such as “The Unsafe Browser can load a web page”, are expected to generate non-Tor traffic.

Subtasks

History

#1 Updated by anonym 2016-04-25 06:56:23

  • Target version set to Tails_2.4

I’ll raise this discussion during the next CI meeting.

#2 Updated by anonym 2016-06-02 14:36:13

  • Target version changed from Tails_2.4 to 2016

anonym wrote:
> I’ll raise this discussion during the next CI meeting.

We have more important things to deal with in the near future => postponing.

#3 Updated by anonym 2016-06-02 14:37:53

#4 Updated by intrigeri 2019-09-07 06:37:17

  • Description updated