Project Number Date
test_Tails_ISO_stable 5696 03 Jun 2025, 13:51

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 19:44.536 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:7.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 32.962
When I start Tails from USB drive "old" with network unplugged 1:29.060
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.552
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:27.593
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 29.158
And I take note of which tps features are available 2.215
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.217
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.310
Then Tails is running from USB drive "old" 0.378
And all tps features are active 1.932
When I write some files expected to persist 1.603
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.351
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.296
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.168
After features/support/hooks.rb:330 0.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.812
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 without a persistent partition and stopped at Tails Greeter's login screen 10.226
And I log in to a new session 18.882
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.926
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.447
Then the running Tails is installed on USB drive "to_upgrade" 25.541
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 4.400
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.300
Then all tps features from the old Tails version are active 1.633
And Tails is running from USB drive "to_upgrade" 0.455
And the boot device has safe access rights 3.467
And the expected persistent files created with the old Tails version are present in the filesystem 1.322
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
7:6.988
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 38.182
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.555
When the network is plugged 0.072
And Tor is ready 17.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.333
Given I shutdown Tails and wait for the computer to power off 8.800
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.302
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 2.128
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.253
When the network is plugged 0.070
And Tor is ready 46.720
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.633
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.970
Given I shutdown Tails and wait for the computer to power off 4.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.917
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.142
And Tor is ready 18.556
Then the Upgrader considers the system as up-to-date 0.306
# 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 15.032
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.565
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
33.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 15.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.029
After features/support/hooks.rb:330 2.685
After features/support/hooks.rb:100 0.000