usb_upgrade.feature

@product
Feature: Upgrading an old Tails USB installation
  As a Tails user
  If I have an old version of Tails installed on a USB device
  and the USB device has a persistent partition
  I want to upgrade Tails on it
  and keep my persistent partition in the process

  # An issue with this feature is that scenarios depend on each
  # other. When editing this feature, make sure you understand these
  # dependencies (which are documented below).

  Scenario: Try cloning Tails to a too small partition
    Given I have started Tails from DVD without network and logged in
    And I temporarily create a 7200 MiB disk named "too-small-partition"
    And I create a 500 MiB gpt partition labeled "Tails" with a vfat filesystem on disk "too-small-partition"
    And I plug USB drive "too-small-partition"
    When I start Tails Installer
    Then I am told by Tails Installer that I "need to use a downloaded Tails ISO image"

  # Installation method inspired by the usb-install-tails-greeter
  # checkpoint, variations are using the old Tails USB image and a
  # different device name ("old" instead of "__internal")
  #
  # Boot the system to make sure resizing has happened, and to check
  # the system is sane (safe access rights, no persistence, etc.); end
  # with unplugging to get both a clean state and a stopped machine.
  Scenario: Installing an old version of Tails to a pristine USB drive
    Given a computer
    And I create a 7200 MiB disk named "old"
    And I plug USB drive "old"
    And I write an old version of the Tails USB image to disk "old"
    When I start Tails from USB drive "old" with network unplugged
    Then the boot device has safe access rights
    And Tails is running from USB drive "old"
    And there is no persistence partition on USB drive "old"
    And process "udev-watchdog" is running
    And udev-watchdog is monitoring the correct device
    And I unplug USB drive "old"

  # Depends on scenario: Installing an old version of Tails to a pristine USB drive
  Scenario: Creating a persistent partition with the old Tails USB installation
    Given a computer
    And I start Tails from USB drive "old" with network unplugged and I login
    Then Tails is running from USB drive "old"
    And I create a persistent partition
    And I take note of which persistence presets are available
    Then a Tails persistence partition exists on USB drive "old"
    And I shutdown Tails and wait for the computer to power off

  # Depends on scenario: Creating a persistent partition with the old Tails USB installation
  Scenario: Writing files to a read/write-enabled persistent partition with the old Tails USB installation
    Given a computer
    And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled
    Then Tails is running from USB drive "old"
    And all persistence presets are enabled
    When I write some files expected to persist
    And all persistent filesystems have safe access rights
    And all persistence configuration files have safe access rights
    And all persistent directories from the old Tails version have safe access rights
    And I take note of which persistence presets are available
    And I shutdown Tails and wait for the computer to power off
    # XXX: how does guestfs work vs snapshots?
    Then only the expected files are present on the persistence partition on USB drive "old"

  # Depends on scenario: Writing files to a read/write-enabled persistent partition with the old Tails USB installation
  Scenario: Upgrading an old Tails USB installation from a Tails DVD
    Given I have started Tails from DVD without network and logged in
    And I clone USB drive "old" to a new USB drive "to_upgrade"
    And I plug USB drive "to_upgrade"
    When I upgrade Tails to USB drive "to_upgrade" by cloning
    Then the running Tails is installed on USB drive "to_upgrade"
    And I unplug USB drive "to_upgrade"

  # Depends on scenario: Upgrading an old Tails USB installation from a Tails DVD
  Scenario: Booting Tails from a USB drive upgraded from DVD with persistence enabled
    Given a computer
    And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled
    Then all persistence presets from the old Tails version are enabled
    And Tails is running from USB drive "to_upgrade"
    And the boot device has safe access rights
    And the expected persistent files created with the old Tails version are present in the filesystem
    And all persistent directories from the old Tails version have safe access rights

  # Depends on scenario: Writing files to a read/write-enabled persistent partition with the old Tails USB installation
  Scenario: Upgrading an old Tails USB installation from another Tails USB drive
    Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen
    And I log in to a new session
    And I clone USB drive "old" to a new USB drive "to_upgrade"
    And I plug USB drive "to_upgrade"
    When I upgrade Tails to USB drive "to_upgrade" by cloning
    Then the running Tails is installed on USB drive "to_upgrade"
    And I unplug USB drive "to_upgrade"
    And I unplug USB drive "__internal"

  # Depends on scenario: Upgrading an old Tails USB installation from another Tails USB drive
  Scenario: Booting Tails from a USB drive upgraded from USB with persistence enabled
    Given a computer
    And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled
    Then all persistence presets from the old Tails version are enabled
    And Tails is running from USB drive "to_upgrade"
    And the boot device has safe access rights
    And the expected persistent files created with the old Tails version are present in the filesystem
    And all persistent directories from the old Tails version have safe access rights

  @automatic_upgrade
  Scenario: Upgrading an initial Tails installation with an incremental upgrade
    Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in
    And no SquashFS delta is installed
    And Tails is fooled to think that version 2.0~test was initially installed
    And the file system changes introduced in version 2.2~test are not present
    And the file system changes introduced in version 2.3~test are not present
    When the network is plugged
    And Tor is ready
    Then I am proposed to install an incremental upgrade to version 2.2~test
    And I can successfully install the incremental upgrade to version 2.2~test
    Given I shutdown Tails and wait for the computer to power off
    When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled
    Then Tails is running version 2.2~test
    And all persistence presets are enabled
    And the file system changes introduced in version 2.2~test are present
    And only the 2.2~test SquashFS delta is installed
    # Our IUK sets a release date that can make Tor bootstrapping impossible
    Given Tails system time is magically synchronized
    # We'll really install Tails_amd64_2.0~test_to_2.3~test.iuk
    # but we need some way to force upgrading a second time in a row
    # even if only the initially installed version is considered
    And Tails is fooled to think that version 2.1~test was initially installed
    When the network is plugged
    And Tor is ready
    Then I am proposed to install an incremental upgrade to version 2.3~test
    And I can successfully install the incremental upgrade to version 2.3~test
    Given I shutdown Tails and wait for the computer to power off
    When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled
    Then Tails is running version 2.3~test
    And all persistence presets are enabled
    And the file system changes introduced in version 2.3~test are present
    And only the 2.3~test SquashFS delta is installed
    # Our IUK sets a release date that can make Tor bootstrapping impossible
    Given Tails system time is magically synchronized
    # Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
    When the network is plugged
    And Tor is ready
    Then I successfully start the Unsafe Browser
    And the file system changes introduced in version 2.3~test are present in the Unsafe Browser's chroot

  @automatic_upgrade
  Scenario: Upgrading a Tails that has several SquashFS deltas present with an incremental upgrade
    Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in
    And Tails is fooled to think that version 2.0~test was initially installed
    And Tails is fooled to think a 2.0.1~test SquashFS delta is installed
    And Tails is fooled to think a 2.1~test SquashFS delta is installed
    When the network is plugged
    And Tor is ready
    Then I am proposed to install an incremental upgrade to version 2.2~test
    And I can successfully install the incremental upgrade to version 2.2~test
    Then only the 2.2~test SquashFS delta is installed

  @automatic_upgrade
  Scenario: Upgrading a Tails whose signing key is outdated
    Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in
    And Tails is fooled to think that version 2.0~test was initially installed
    And the signing key used by the Upgrader is outdated
    But a current signing key is available on our website
    When the network is plugged
    And Tor is ready
    Then I am proposed to install an incremental upgrade to version 2.2~test