Project Number Date
test_Tails_ISO_closed-issues-design-doc 1 28 May 2026, 17:57

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 12:33.257 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:28.708
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.537
When I start Tails from USB drive "old" with network unplugged 1:8.676
Then the boot device has safe access rights 3.472
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:335 3.558
After features/support/hooks.rb:104 0.008
Tags: @product
1:36.779
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 59.177
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 28.957
And I take note of which tps features are available 0.383
Then a Tails persistence partition exists on USB drive "old" 0.663
And I shutdown Tails and wait for the computer to power off 7.246
After features/support/hooks.rb:335 0.646
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.070
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.374
Then Tails is running from USB drive "old" 0.228
And all tps features are active 1.226
When I write some files expected to persist 1.757
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.073
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 4.208
# 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" 13.400
After features/support/hooks.rb:335 0.238
After features/support/hooks.rb:104 0.006
Tags: @product
2:16.829
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 9.150
And I log in to a new session 14.950
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.978
And I plug USB drive "to_upgrade" 2.309
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.026
Then the running Tails is installed on USB drive "to_upgrade" 17.131
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 3.287
After features/support/hooks.rb:104 0.000
Tags: @product
1:17.639
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.765
Then all tps features from the old Tails version are active 1.073
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.778
And the expected persistent files created with the old Tails version are present in the filesystem 1.345
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:335 0.798
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
4:1.579
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.913
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.022
And Tor is ready 13.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.798
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.271
Given I shutdown Tails and wait for the computer to power off 11.034
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.090
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.243
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.196
When the network is plugged 0.018
And Tor is ready 10.322
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.707
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.691
Given I shutdown Tails and wait for the computer to power off 8.748
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.352
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.022
And Tor is ready 11.689
Then the Upgrader considers the system as up-to-date 10.553
# 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.338
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.548
After features/support/hooks.rb:335 1.098
After features/support/hooks.rb:104 0.038
Tags: @product @automatic_upgrade
20.651
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.337
After features/support/hooks.rb:335 0.657
After features/support/hooks.rb:104 0.000