Project Number Date
test_Tails_ISO_stable 6378 14 May 2026, 22:54

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:45.423 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:11.187
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.376
When I start Tails from USB drive "old" with network unplugged 53.262
Then the boot device has safe access rights 2.817
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:335 1.226
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.670
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 55.966
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 26.514
And I take note of which tps features are available 0.360
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 6.998
After features/support/hooks.rb:335 0.217
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.909
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.991
Then Tails is running from USB drive "old" 0.325
And all tps features are active 1.148
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 2.009
And I take note of which tps features are available 0.182
And I shutdown Tails and wait for the computer to power off 8.399
# 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" 12.012
After features/support/hooks.rb:335 0.456
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.226
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.953
And I log in to a new session 12.541
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.760
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.367
Then the running Tails is installed on USB drive "to_upgrade" 16.057
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:335 0.720
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.459
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:5.724
Then all tps features from the old Tails version are active 1.139
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.704
And the expected persistent files created with the old Tails version are present in the filesystem 1.069
And all persistent directories from the old Tails version have safe access rights 2.478
After features/support/hooks.rb:335 0.821
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:47.361
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.599
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.016
And Tor is ready 14.007
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.777
Given I shutdown Tails and wait for the computer to power off 11.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.819
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.121
And the file system changes introduced in version 6.2~testoverlayfs are present 0.262
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.192
When the network is plugged 0.013
And Tor is ready 10.161
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.901
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.177
Given I shutdown Tails and wait for the computer to power off 8.049
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.426
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.252
And the file system changes introduced in version 6.3~testoverlayfs are present 0.416
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.016
And Tor is ready 10.007
Then the Upgrader considers the system as up-to-date 10.499
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:335 1.085
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.608
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.322
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.668
After features/support/hooks.rb:335 0.613
After features/support/hooks.rb:104 0.000