Project Number Date
test_Tails_ISO_stable 6511 19 Jul 2026, 12:04

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:13.756 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:10.251
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.092
When I start Tails from USB drive "old" with network unplugged 51.594
Then the boot device has safe access rights 2.830
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.848
After features/support/hooks.rb:108 0.026
Tags: @product
1:32.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 54.799
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 24.264
And I take note of which tps features are available 4.342
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 8.075
After features/support/hooks.rb:339 0.596
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.022
Then Tails is running from USB drive "old" 0.264
And all tps features are active 4.929
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.293
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.044
And I take note of which tps features are available 4.219
And I shutdown Tails and wait for the computer to power off 6.675
# 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.449
After features/support/hooks.rb:339 0.184
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.261
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.879
And I log in to a new session 12.819
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.904
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.610
Then the running Tails is installed on USB drive "to_upgrade" 15.497
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 2.242
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.578
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.272
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.566
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.410
And the expected persistent files created with the old Tails version are present in the filesystem 1.193
And all persistent directories from the old Tails version have safe access rights 2.004
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
4:0.326
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.453
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
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.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.027
And Tor is ready 11.945
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.269
Given I shutdown Tails and wait for the computer to power off 9.521
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.700
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.227
When the network is plugged 0.016
And Tor is ready 9.854
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.491
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.569
Given I shutdown Tails and wait for the computer to power off 7.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.313
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.580
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.015
And Tor is ready 10.233
Then the Upgrader considers the system as up-to-date 10.567
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:339 0.649
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
21.405
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.870
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.221
After features/support/hooks.rb:339 0.847
After features/support/hooks.rb:108 0.000