Project Number Date
test_Tails_ISO_stable 5967 24 Nov 2025, 21:11

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 17:20.906 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:22.201
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 33.642
When I start Tails from USB drive "old" with network unplugged 1:42.845
Then the boot device has safe access rights 3.002
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.143
And process "udev-watchdog" is running 0.136
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.489
After features/support/hooks.rb:331 4.201
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:29.865
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 32.422
And I take note of which tps features are available 1.402
Then a Tails persistence partition exists on USB drive "old" 0.687
And I shutdown Tails and wait for the computer to power off 8.229
After features/support/hooks.rb:331 0.301
After features/support/hooks.rb:100 0.011
Tags: @product
2:19.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.499
Then Tails is running from USB drive "old" 1.052
And all tps features are active 2.433
When I write some files expected to persist 1.901
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.581
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 7.761
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.128
After features/support/hooks.rb:331 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.805
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 13.170
And I log in to a new session 12.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.343
And I plug USB drive "to_upgrade" 2.585
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.454
Then the running Tails is installed on USB drive "to_upgrade" 23.023
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:331 6.935
After features/support/hooks.rb:100 0.000
Tags: @product
1:51.034
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.686
Then all tps features from the old Tails version are active 2.350
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.633
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.255
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:11.570
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 with a persistent partition enabled and logged in 13.147
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.060
And Tor is ready 13.397
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.571
Given I shutdown Tails and wait for the computer to power off 9.078
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.091
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.714
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.287
When the network is plugged 0.058
And Tor is ready 11.830
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.452
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.189
Given I shutdown Tails and wait for the computer to power off 3.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.446
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.595
And the file system changes introduced in version 6.3~testoverlayfs are present 0.764
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.068
And Tor is ready 12.007
Then the Upgrader considers the system as up-to-date 0.199
# 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 5.930
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.176
After features/support/hooks.rb:331 0.753
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
51.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.944
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 39.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.586
After features/support/hooks.rb:331 1.333
After features/support/hooks.rb:100 0.000