Feature #10834

Write a test for re-configuring an existing persistent volume

Added by intrigeri 2016-01-01 10:40:34 . Updated 2016-06-08 01:25:07 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_2.4
Start date:
2016-01-01
Due date:
% Done:

100%

Feature Branch:
test/10834-reconfigure-persistent-volume
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

Apparently, in the test suite we only use t-p-s to set up new persistent volumes, but we don’t test using it to configure it an existing one that was enabled in the Greeter (otherwise, Bug #10809 would have been noticed earlier, presumably). Can we please have a simple test for that?

Subtasks

Related issues

Related to Tails - Bug #10809: Can't configure persistent volume on Jessie Resolved 2015-12-31

History

#1 Updated by intrigeri 2016-01-01 10:41:24

  • Description updated

#2 Updated by intrigeri 2016-01-01 10:41:34

  • related to Bug #10809: Can't configure persistent volume on Jessie added

#3 Updated by intrigeri 2016-01-01 10:41:48

  • Subject changed from Write a test for configuring a pre-existent persistent volume to Write a test for re-configuring an existing persistent volume

#4 Updated by intrigeri 2016-03-03 15:58:26

  • Assignee changed from kytv to intrigeri
  • Target version changed from Tails_2.2 to Tails_2.4

#5 Updated by intrigeri 2016-03-03 15:59:47

#6 Updated by intrigeri 2016-04-16 15:41:01

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

#7 Updated by intrigeri 2016-05-03 11:55:39

  • Status changed from Confirmed to In Progress

Applied in changeset commit:95034ea119dcaf8de7920037b421d4e562a90065.

#8 Updated by intrigeri 2016-05-04 08:37:01

  • Assignee changed from intrigeri to anonym
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to test/10834-reconfigure-persistent-volume

#9 Updated by anonym 2016-05-09 03:22:22

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

#10 Updated by anonym 2016-06-08 01:25:07

  • Status changed from Fix committed to Resolved