Project Number Date
test_Tails_ISO_devel 4527 02 Aug 2026, 11:17

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:19.618 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:5.459
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
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.209
When I start Tails from USB drive "old" with network unplugged 47.974
Then the boot device has safe access rights 2.530
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.690
After features/support/hooks.rb:108 0.047
Tags: @product
1:24.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.131
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 23.582
And I take note of which tps features are available 3.983
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 4.022
After features/support/hooks.rb:339 0.243
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.830
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.544
Then Tails is running from USB drive "old" 0.273
And all tps features are active 4.722
When I write some files expected to persist 1.364
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 1.968
And I take note of which tps features are available 3.622
And I shutdown Tails and wait for the computer to power off 4.115
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.658
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.763
And I log in to a new session 12.320
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.734
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.217
Then the running Tails is installed on USB drive "to_upgrade" 14.083
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 2.153
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.155
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.186
Then all tps features from the old Tails version are active 0.958
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.125
And all persistent directories from the old Tails version have safe access rights 1.861
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
3:40.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.975
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.018
And Tor is ready 12.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.127
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.151
Given I shutdown Tails and wait for the computer to power off 5.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.863
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.372
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.198
When the network is plugged 0.014
And Tor is ready 10.602
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.202
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.827
Given I shutdown Tails and wait for the computer to power off 3.961
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.886
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.651
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.012
And Tor is ready 9.872
Then the Upgrader considers the system as up-to-date 10.482
# 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.212
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:339 1.029
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.083
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.321
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.415
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.000