Project Number Date
test_Tails_ISO_stable 5612 30 Apr 2025, 08:58

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 18:53.109 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:3.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.180
When I start Tails from USB drive "old" with network unplugged 1:27.648
Then the boot device has safe access rights 2.936
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.732
After features/support/hooks.rb:100 0.007
Tags: @product
2:3.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:21.564
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 30.118
And I take note of which tps features are available 2.290
Then a Tails persistence partition exists on USB drive "old" 0.755
And I shutdown Tails and wait for the computer to power off 8.422
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.752
Then Tails is running from USB drive "old" 1.524
And all tps features are active 1.925
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.439
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 6.216
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.943
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.385
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.697
And I log in to a new session 19.801
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.553
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.077
Then the running Tails is installed on USB drive "to_upgrade" 20.385
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:330 1.044
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.012
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.641
Then all tps features from the old Tails version are active 1.559
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.443
And the expected persistent files created with the old Tails version are present in the filesystem 1.433
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:330 1.105
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:24.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.192
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.075
And Tor is ready 23.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.013
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.455
Given I shutdown Tails and wait for the computer to power off 8.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.537
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.295
When the network is plugged 0.071
And Tor is ready 19.955
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.732
Given I shutdown Tails and wait for the computer to power off 4.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.120
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.076
And Tor is ready 17.179
Then the Upgrader considers the system as up-to-date 0.301
# 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 14.895
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.584
After features/support/hooks.rb:330 0.740
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
41.758
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.536
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.103
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 22.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.864
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.000