Project Number Date
test_Tails_ISO_stable 6373 13 May 2026, 11:22

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 10:58.019 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:0.816
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.835
When I start Tails from USB drive "old" with network unplugged 43.813
Then the boot device has safe access rights 2.388
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 3.747
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.338
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 52.371
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.831
And I take note of which tps features are available 0.328
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 8.017
After features/support/hooks.rb:335 0.516
After features/support/hooks.rb:104 0.007
Tags: @product
1:18.711
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.048
Then Tails is running from USB drive "old" 0.219
And all tps features are active 1.271
When I write some files expected to persist 1.353
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 1.925
And I take note of which tps features are available 0.247
And I shutdown Tails and wait for the computer to power off 2.673
# 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.418
After features/support/hooks.rb:335 0.108
After features/support/hooks.rb:104 0.007
Tags: @product
2:7.845
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.803
And I log in to a new session 11.784
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.621
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.733
Then the running Tails is installed on USB drive "to_upgrade" 14.411
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 2.249
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.456
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.047
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.016
And all persistent directories from the old Tails version have safe access rights 1.748
After features/support/hooks.rb:335 0.787
After features/support/hooks.rb:104 0.006
3:38.538
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 with a persistent partition enabled and logged in 7.987
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.017
And Tor is ready 13.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.847
Given I shutdown Tails and wait for the computer to power off 10.799
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.772
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.232
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.229
When the network is plugged 0.027
And Tor is ready 10.020
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.561
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.817
Given I shutdown Tails and wait for the computer to power off 7.883
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.892
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.014
And Tor is ready 10.902
Then the Upgrader considers the system as up-to-date 10.493
# 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.118
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.423
After features/support/hooks.rb:335 0.816
After features/support/hooks.rb:104 0.010
20.311
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 with a persistent partition enabled and logged in 7.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.997
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.796
After features/support/hooks.rb:335 0.902
After features/support/hooks.rb:104 0.000