Feature #15238

Iteration 1: Write tests for unlocking VeraCrypt partitions in GNOME

Added by segfault 2018-01-25 11:51:52 . Updated 2018-12-16 13:39:11 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Test suite
Target version:
Tails_3.11
Start date:
2018-01-25
Due date:
% Done:

100%

Feature Branch:
test/14471-veracrypt
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
299

Description

Subtasks

Related issues

Blocks Tails - Feature #14471: Write tests for VeraCrypt support in GNOME Disks Resolved 2017-08-28
Blocked by Tails - Feature #15628: Consider re-enabling automounting to improve VeraCrypt UX Resolved 2018-05-30

History

#1 Updated by segfault 2018-01-25 12:16:07

  • Category set to Test suite

#2 Updated by segfault 2018-01-25 15:25:47

  • Target version changed from Tails_3.9 to Tails_3.7

#3 Updated by segfault 2018-01-25 16:01:43

  • Subject changed from Write tests for unlocking VeraCrypt partitions in GNOME to Iteration 1: Write tests for unlocking VeraCrypt partitions in GNOME

#4 Updated by intrigeri 2018-03-28 09:25:09

  • Priority changed from Normal to Elevated

#5 Updated by intrigeri 2018-05-07 14:06:21

  • Target version changed from Tails_3.7 to Tails_3.8

#6 Updated by intrigeri 2018-05-25 13:20:49

  • Target version changed from Tails_3.8 to Tails_3.9

#8 Updated by intrigeri 2018-06-03 12:58:16

  • blocks Feature #14471: Write tests for VeraCrypt support in GNOME Disks added

#9 Updated by intrigeri 2018-06-10 16:34:55

  • blocked by Feature #15628: Consider re-enabling automounting to improve VeraCrypt UX added

#10 Updated by intrigeri 2018-06-10 16:37:57

FTR, while looking at test suite results for the VeraCrypt beta, I’ve noticed that commit:c707d4f128821f402fc398085f3c227bb05575fc (“Enable automounting of media”) breaks big parts of the test suite: various notifications and prompts hide the parts of the screen we’re looking for. Sadly, this prevents us from using our test suite to gain confidence in the VeraCrypt patch set. Anyway, let’s first decide something on Feature #15628 and let’s not spend time now adapting the test suite to this change.

#11 Updated by intrigeri 2018-06-26 17:14:22

  • Assignee changed from anonym to intrigeri
  • Target version changed from Tails_3.9 to Tails_3.10.1

#13 Updated by intrigeri 2018-09-12 16:17:20

  • Feature Branch set to test/14471-veracrypt

#14 Updated by intrigeri 2018-09-12 20:46:11

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

#15 Updated by intrigeri 2018-09-13 16:29:30

  • % Done changed from 10 to 20

Done for Unlock VeraCrypt Volumes, let’s see what Jenkins thinks. TBD: GNOME Disks.

#16 Updated by intrigeri 2018-09-13 18:30:40

  • % Done changed from 20 to 30
  • QA Check set to Ready for QA

Done for GNOME Disks too.

#17 Updated by intrigeri 2018-09-13 20:09:40

Everything implemented and works locally, now waiting for Jenkins results.

#18 Updated by intrigeri 2018-09-15 05:22:32

  • % Done changed from 30 to 50

These tests now seem pretty solid to me but before requesting a review I need to make the file container ones more robust => see you on Feature #15239.

#19 Updated by intrigeri 2018-09-18 14:42:49

  • Assignee changed from intrigeri to CyrilBrulebois

#20 Updated by intrigeri 2018-10-24 17:03:39

  • Target version changed from Tails_3.10.1 to Tails_3.11

#21 Updated by intrigeri 2018-11-01 14:22:53

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:tails|d01d4b2b1cf60fac8d33c19a82448b6bd49ca403.

#22 Updated by intrigeri 2018-11-01 14:24:18

  • Assignee deleted (CyrilBrulebois)
  • QA Check changed from Ready for QA to Pass

Reviewed pass as per Feature #14471#note-24.

#23 Updated by CyrilBrulebois 2018-12-16 13:39:11

  • Status changed from Fix committed to Resolved