1 files changed, 55 insertions, 0 deletions
diff --git a/features/persistence.feature b/features/persistence.feature
new file mode 100644
index 00000000..13f0af70
--- /dev/null
+++ b/features/persistence.feature
@@ -0,0 +1,55 @@
+#10720: Tails Installer freezes on Jenkins
+@product @fragile
+Feature: Tails persistence
+  As a Tails user
+  I want to use Tails persistence feature
+
+  Scenario: Booting Tails from a USB drive with a disabled persistent partition
+    Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
+    When I log in to a new session
+    Then Tails seems to have booted normally
+    And Tails is running from USB drive "__internal"
+    And persistence is disabled
+    But a Tails persistence partition exists on USB drive "__internal"
+
+  Scenario: Booting Tails from a USB drive with an enabled persistent partition
+    Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in
+    Then Tails is running from USB drive "__internal"
+    And all persistence presets are enabled
+    And all persistent directories have safe access rights
+
+  @fragile
+  Scenario: Writing files first to a read/write-enabled persistent partition, and then to a read-only-enabled persistent partition
+    Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in
+    And the network is plugged
+    And Tor is ready
+    And I take note of which persistence presets are available
+    When I write some files expected to persist
+    And I add a wired DHCP NetworkManager connection called "persistent-con"
+    And I shutdown Tails and wait for the computer to power off
+    # XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?
+    Then only the expected files are present on the persistence partition on USB drive "__internal"
+    Given I start Tails from USB drive "__internal" with network unplugged and I login with read-only persistence enabled
+    And the network is plugged
+    And Tor is ready
+    Then Tails is running from USB drive "__internal"
+    And the boot device has safe access rights
+    And all persistence presets are enabled
+    And I switch to the "persistent-con" NetworkManager connection
+    And there is no GNOME bookmark for the persistent Tor Browser directory
+    And I write some files not expected to persist
+    And I remove some files expected to persist
+    And I take note of which persistence presets are available
+    And I shutdown Tails and wait for the computer to power off
+    Then only the expected files are present on the persistence partition on USB drive "__internal"
+
+  Scenario: Deleting a Tails persistent partition
+    Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen
+    And I log in to a new session
+    Then Tails is running from USB drive "__internal"
+    And the boot device has safe access rights
+    And persistence is disabled
+    But a Tails persistence partition exists on USB drive "__internal"
+    And all notifications have disappeared
+    When I delete the persistent partition
+    Then there is no persistence partition on USB drive "__internal"