Project Number Date
test_Tails_ISO_devel 4465 22 Jun 2026, 12:11

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:40.286 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:15.796
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.089
When I start Tails from USB drive "old" with network unplugged 57.279
Then the boot device has safe access rights 2.612
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 1.484
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.175
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 56.170
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 25.927
And I take note of which tps features are available 5.256
Then a Tails persistence partition exists on USB drive "old" 0.688
And I shutdown Tails and wait for the computer to power off 6.857
After features/support/hooks.rb:339 0.217
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.404
Then Tails is running from USB drive "old" 0.333
And all tps features are active 5.724
When I write some files expected to persist 1.374
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.333
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 4.031
And I shutdown Tails and wait for the computer to power off 8.225
# 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.369
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.534
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.698
And I log in to a new session 14.339
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.864
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.438
Then the running Tails is installed on USB drive "to_upgrade" 17.645
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.232
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.075
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.543
Then all tps features from the old Tails version are active 1.163
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.304
And all persistent directories from the old Tails version have safe access rights 1.987
After features/support/hooks.rb:339 0.739
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:10.212
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.214
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.020
And Tor is ready 13.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.004
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.144
Given I shutdown Tails and wait for the computer to power off 11.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.112
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 5.518
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.190
When the network is plugged 0.021
And Tor is ready 11.419
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.797
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.189
Given I shutdown Tails and wait for the computer to power off 4.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.890
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.261
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.022
And Tor is ready 11.210
Then the Upgrader considers the system as up-to-date 10.618
# 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 5.036
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.519
After features/support/hooks.rb:339 0.827
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
21.485
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.691
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.284
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.128
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.000