Project Number Date
test_Tails_ISO_stable-flatpak 54 23 Oct 2026, 19:50

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:32.804 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.864
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.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.897
When I start Tails from USB drive "old" with network unplugged 53.978
Then the boot device has safe access rights 2.126
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.703
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 50.329
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 24.870
And I take note of which tps features are available 6.374
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 4.017
After features/support/hooks.rb:339 0.360
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.468
Then Tails is running from USB drive "old" 0.185
And all tps features are active 7.727
When I write some files expected to persist 1.316
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.983
And I take note of which tps features are available 5.674
And I shutdown Tails and wait for the computer to power off 2.554
# 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.490
After features/support/hooks.rb:339 0.438
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.216
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.240
And I log in to a new session 11.503
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.191
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.743
Then the running Tails is installed on USB drive "to_upgrade" 18.660
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.131
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.122
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.999
Then all tps features from the old Tails version are active 1.120
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 2.067
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.222
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.085
Tags: @product @automatic_upgrade
3:34.670
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.440
And no SquashFS delta is installed 0.097
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.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.025
And Tor is ready 12.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.469
Given I shutdown Tails and wait for the computer to power off 6.700
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.825
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.171
When the network is plugged 0.027
And Tor is ready 10.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.775
Given I shutdown Tails and wait for the computer to power off 2.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.196
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.790
And the file system changes introduced in version 6.3~testoverlayfs are present 0.239
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.155
When the network is plugged 0.030
And Tor is ready 10.337
Then the Upgrader considers the system as up-to-date 0.129
# 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.512
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:339 0.719
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.547
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.057
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.681
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.649
After features/support/hooks.rb:339 0.729
After features/support/hooks.rb:108 0.000