Project Number Date
test_Tails_ISO_stable 6491 07 Jul 2026, 11:34

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:43.849 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:6.772
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.485
When I start Tails from USB drive "old" with network unplugged 49.056
Then the boot device has safe access rights 2.486
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.782
After features/support/hooks.rb:108 0.012
Tags: @product
1:30.368
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 52.290
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 24.688
And I take note of which tps features are available 4.473
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 8.051
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.728
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.043
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.005
Then Tails is running from USB drive "old" 0.243
And all tps features are active 4.694
When I write some files expected to persist 1.371
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.905
And I take note of which tps features are available 3.955
And I shutdown Tails and wait for the computer to power off 8.162
# 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.885
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.180
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.131
And I log in to a new session 13.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.894
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.124
Then the running Tails is installed on USB drive "to_upgrade" 15.177
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 7.044
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.572
Then all tps features from the old Tails version are active 0.928
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.304
And the expected persistent files created with the old Tails version are present in the filesystem 1.013
And all persistent directories from the old Tails version have safe access rights 1.780
After features/support/hooks.rb:339 0.838
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
3:50.760
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.935
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.017
And Tor is ready 12.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.910
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.855
Given I shutdown Tails and wait for the computer to power off 9.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.688
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.885
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
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.132
# 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.232
When the network is plugged 0.013
And Tor is ready 10.905
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.718
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.488
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:5.711
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.926
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.031
And Tor is ready 10.096
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.234
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:339 0.730
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.169
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.369
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.017
And Tor is ready 9.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.502
After features/support/hooks.rb:339 0.569
After features/support/hooks.rb:108 0.000