Project Number Date
test_Tails_ISO_stable 4870 04 Jun 2024, 13:37

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 22:49.191 Passed
Tags: @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 Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
3:2.009
Before features/support/hooks.rb:265 0.006
Given a computer 0.531
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 1:12.657
When I start Tails from USB drive "old" with network unplugged 1:43.128
Then the boot device has safe access rights 3.447
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:311 3.547
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.570
Before features/support/hooks.rb:265 0.005
Given a computer 0.331
And I start Tails from USB drive "old" with network unplugged and I login 1:42.906
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 40.118
And I take note of which tps features are available 1.746
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 9.223
After features/support/hooks.rb:311 0.240
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.942
Before features/support/hooks.rb:265 0.007
Given a computer 0.323
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.598
Then Tails is running from USB drive "old" 0.428
And all tps features are active 2.593
When I write some files expected to persist 2.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.812
And I take note of which tps features are available 0.654
And I shutdown Tails and wait for the computer to power off 4.418
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.043
After features/support/hooks.rb:311 0.226
After features/support/hooks.rb:100 0.012
Tags: @product
2:51.356
Before features/support/hooks.rb:265 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.182
And I log in to a new session 23.640
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.353
And I plug USB drive "to_upgrade" 2.640
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.369
Then the running Tails is installed on USB drive "to_upgrade" 22.703
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:311 3.706
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.404
Before features/support/hooks.rb:265 0.006
Given a computer 0.316
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.636
Then all tps features from the old Tails version are active 1.975
And Tails is running from USB drive "to_upgrade" 0.443
And the boot device has safe access rights 3.740
And the expected persistent files created with the old Tails version are present in the filesystem 1.669
And all persistent directories from the old Tails version have safe access rights 2.623
After features/support/hooks.rb:311 1.092
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:48.091
Before features/support/hooks.rb:265 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.218
And no SquashFS delta is installed 0.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.054
And Tor is ready 21.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.914
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.479
Given I shutdown Tails and wait for the computer to power off 12.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.276
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.850
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.109
And Tor is ready 20.556
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.086
Given I shutdown Tails and wait for the computer to power off 6.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.707
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.804
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.342
When the network is plugged 0.066
And Tor is ready 18.052
Then the Upgrader considers the system as up-to-date 10.927
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 19.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.194
After features/support/hooks.rb:311 1.053
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
45.817
Before features/support/hooks.rb:265 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.680
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 1.193
But a current signing key is available on our website 0.000
When the network is plugged 0.110
And Tor is ready 22.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.630
After features/support/hooks.rb:311 0.995
After features/support/hooks.rb:100 0.000