Project Number Date
test_Tails_ISO_devel 3431 18 Jun 2024, 12:41

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 20:29.213 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
2:13.603
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 40.212
When I start Tails from USB drive "old" with network unplugged 1:28.242
Then the boot device has safe access rights 2.839
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:320 8.764
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.891
Before features/support/hooks.rb:269 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:20.905
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 34.802
And I take note of which tps features are available 1.369
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.523
After features/support/hooks.rb:320 0.160
After features/support/hooks.rb:100 0.012
Tags: @product
2:44.361
Before features/support/hooks.rb:269 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.388
Then Tails is running from USB drive "old" 0.383
And all tps features are active 2.058
When I write some files expected to persist 1.696
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.480
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.471
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.605
After features/support/hooks.rb:320 0.095
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.832
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.012
And I log in to a new session 18.848
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.705
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.555
Then the running Tails is installed on USB drive "to_upgrade" 17.795
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:320 2.085
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.165
Before features/support/hooks.rb:269 0.007
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.771
Then all tps features from the old Tails version are active 1.553
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.034
And the expected persistent files created with the old Tails version are present in the filesystem 1.631
And all persistent directories from the old Tails version have safe access rights 2.559
After features/support/hooks.rb:320 0.756
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:41.550
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.543
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.042
And Tor is ready 21.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.721
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.249
Given I shutdown Tails and wait for the computer to power off 9.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.235
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.392
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.261
When the network is plugged 0.047
And Tor is ready 19.144
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.478
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.203
Given I shutdown Tails and wait for the computer to power off 58.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.212
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.037
And Tor is ready 19.460
Then the Upgrader considers the system as up-to-date 0.319
# 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 13.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.300
After features/support/hooks.rb:320 0.699
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
57.809
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.883
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 1.322
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 45.516
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.599
After features/support/hooks.rb:320 0.603
After features/support/hooks.rb:100 0.000