Project Number Date
test_Tails_ISO_stable 6735 11 Oct 2026, 11:29

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:5.066 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:4.899
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.110
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.590
When I start Tails from USB drive "old" with network unplugged 47.575
Then the boot device has safe access rights 1.954
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.646
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.209
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.907
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 23.316
And I take note of which tps features are available 6.282
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 3.869
After features/support/hooks.rb:339 0.094
After features/support/hooks.rb:108 0.019
Tags: @product
1:32.864
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.175
Then Tails is running from USB drive "old" 0.274
And all tps features are active 7.326
When I write some files expected to persist 1.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.292
And all persistent directories from the old Tails version have safe access rights 1.853
And I take note of which tps features are available 5.926
And I shutdown Tails and wait for the computer to power off 2.629
# 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.803
After features/support/hooks.rb:339 0.404
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.449
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 without a persistent partition and stopped at Tails Greeter's login screen 8.200
And I log in to a new session 11.918
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.649
And I plug USB drive "to_upgrade" 2.189
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.977
Then the running Tails is installed on USB drive "to_upgrade" 17.274
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.663
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.386
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.268
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.206
And the expected persistent files created with the old Tails version are present in the filesystem 0.962
And all persistent directories from the old Tails version have safe access rights 1.550
After features/support/hooks.rb:339 0.754
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:27.442
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 with a persistent partition enabled and logged in 8.154
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.023
And Tor is ready 12.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.334
Given I shutdown Tails and wait for the computer to power off 5.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.173
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 8.393
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.151
When the network is plugged 0.026
And Tor is ready 10.636
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.311
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.584
Given I shutdown Tails and wait for the computer to power off 3.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.644
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.150
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.037
And Tor is ready 10.131
Then the Upgrader considers the system as up-to-date 0.087
# 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 3.562
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:339 0.825
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.812
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.982
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.037
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.131
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.000