Tails Installer: test that the user can install without cloning
The following discussion from !1128 (merged) should be addressed:
-
@boyska started a discussion: We should test that the user can actually install a new Tails without cloning the persistent storage only because they have one. Let's do that as a followup, though.
commit 7995a72d5ac3627576c282d2b1c21513dab03be9 Author: boyska <boyska@riseup.net> Date: Thu Jun 8 16:28:14 2023 +0200 test: user can install w/o cloning diff --git a/features/usb_install.feature b/features/usb_install.feature index 6558c1e1a3..03a6490558 100644 --- a/features/usb_install.feature +++ b/features/usb_install.feature @@ -50,15 +50,14 @@ Feature: Installing Tails to a USB drive And there is a persistence partition on USB drive "install" And the USB drive "install" contains the same files as my persistent storage - Scenario: Cloning Tails with Persistent Storage with Tails Installer to a pristine USB drive + Scenario: Installing Tails with Tails Installer to a pristine USB drive Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in And I create a file in the Persistent directory And I temporarily create a 7200 MiB disk named "install" And I plug USB drive "install" - And I install Tails with Persistent Storage to USB drive "install" by cloning + And I install Tails to USB drive "install" by cloning Then the running Tails is installed on USB drive "install" - And there is a persistence partition on USB drive "install" - And the USB drive "install" contains the same files as my persistent storage + And there is no persistence partition on USB drive "install" Scenario: Re-installing Tails over an existing USB installation with a persistent partition # We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.