Project

General

Profile

Feature #11376

Feature #10237: Refactor and clean up the automated test suite

Remove @check_tor_leaks tag and always look for leaks

Added by anonym over 3 years ago. Updated 2 months ago.

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

0%

Feature Branch:
Type of work:
Discuss
Blueprint:
Starter:
Affected tool:

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 #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.

History

#1 Updated by anonym over 3 years ago

  • Target version set to Tails_2.4

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

#2 Updated by anonym over 3 years ago

  • 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 over 3 years ago

  • Target version deleted (2016)
  • Parent task set to #10237

#4 Updated by intrigeri 2 months ago

  • Description updated (diff)

Also available in: Atom PDF