Project Number Date
test_Tails_ISO_stable 6037 05 Jan 2026, 18:13

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 11:14.521 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
1:17.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.356
When I start Tails from USB drive "old" with network unplugged 59.721
Then the boot device has safe access rights 2.507
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 3.995
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.976
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.358
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 23.075
And I take note of which tps features are available 0.681
Then a Tails persistence partition exists on USB drive "old" 0.516
And I shutdown Tails and wait for the computer to power off 8.011
After features/support/hooks.rb:331 0.353
After features/support/hooks.rb:100 0.006
Tags: @product
1:17.109
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.468
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.053
When I write some files expected to persist 1.324
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.995
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 2.631
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.712
After features/support/hooks.rb:331 0.187
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.013
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.375
And I log in to a new session 12.242
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.206
Then the running Tails is installed on USB drive "to_upgrade" 15.930
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 3.825
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.302
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.285
Then all tps features from the old Tails version are active 0.995
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.642
And the expected persistent files created with the old Tails version are present in the filesystem 1.106
And all persistent directories from the old Tails version have safe access rights 1.978
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:36.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.011
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.015
And Tor is ready 12.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.851
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.263
Given I shutdown Tails and wait for the computer to power off 9.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.565
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.029
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.193
When the network is plugged 0.015
And Tor is ready 10.787
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.298
Given I shutdown Tails and wait for the computer to power off 7.986
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.198
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.019
And Tor is ready 12.241
Then the Upgrader considers the system as up-to-date 10.535
# 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 4.255
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
20.524
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.697
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.140
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.000