Feature #5707

Test suite: split various checks feature

Added by Tails 2013-07-18 07:44:51 . Updated 2016-09-20 16:47:13 .

Test suite
Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


As currently implemented, checks.feature mixes various unrelated checks for the sole reason of improving the test suite runtime. Unfortunately, this is deemed to result in a quickly growing bitrot space.

Instead, the scenarii that are currently in there should be split into functionally grouped independent features, that would share a tag expressing that they can share a common background snapshot.


Related issues

Blocked by Tails - Feature #6094: Test suite: background snapshot improvements Resolved 2015-10-15


#1 Updated by intrigeri 2013-10-04 06:56:31

  • Category set to Test suite
  • Starter set to No

#2 Updated by BitingBird 2014-06-09 11:02:49

  • Subject changed from test suite: split various checks feature to Test suite: split various checks feature

#3 Updated by anonym 2015-01-09 13:48:25

  • blocked by Feature #6094: Test suite: background snapshot improvements added

#4 Updated by anonym 2015-01-10 06:39:37

  • Target version set to Tails_2.4

#5 Updated by anonym 2015-01-10 17:17:05

  • blocks #8668 added

#7 Updated by anonym 2015-09-26 08:46:35

  • Assignee set to anonym

#8 Updated by anonym 2016-05-10 07:35:46

  • Deliverable for changed from 270 to SponsorS_Internal

#9 Updated by intrigeri 2016-05-10 07:42:09

  • Priority changed from Normal to Elevated
  • Deliverable for changed from SponsorS_Internal to 270

#11 Updated by intrigeri 2016-05-18 13:20:02

  • Priority changed from Elevated to High

#12 Updated by anonym 2016-06-02 20:30:44

  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to bertagaz
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to test/5707-split-checks.feature

There’s some serious lack of imagination in the topic branch, I guess. Suggestions of improvements are welcome! Also I skipped the As a Tails user/developer... intro text since I find it a worthless exercise in semi-creative writing. If someone can point out to me what problem it is supposed to solve I’ll give it a try.

#13 Updated by bertagaz 2016-06-07 12:31:32

  • Target version changed from Tails_2.4 to Tails_2.5

#14 Updated by bertagaz 2016-07-20 05:10:04

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

Code review didn’t give me much more inspiration, so it seems fine to me as it is. Running the new features does not raise any issue either, so merged it, congrats!

#15 Updated by intrigeri 2016-07-20 10:09:41

  • Status changed from Resolved to Fix committed
  • Target version changed from Tails_2.5 to Tails_2.6

(Seems like this was merged into devel only, so it can’t be in 2.5. And it’s “Fix committed” until we’ve released.)

#16 Updated by anonym 2016-09-20 16:47:13

  • Status changed from Fix committed to Resolved