Project Number Date
test_Tails_ISO_stable-flatpak 39 07 Oct 2026, 19:51

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:25.104 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:2.685
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.101
When I start Tails from USB drive "old" with network unplugged 45.987
Then the boot device has safe access rights 1.828
And Tails is running from USB drive "old" 0.196
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:339 3.845
After features/support/hooks.rb:108 0.012
Tags: @product
1:22.338
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 48.025
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 23.951
And I take note of which tps features are available 6.768
Then a Tails persistence partition exists on USB drive "old" 0.609
And I shutdown Tails and wait for the computer to power off 2.605
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.933
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.212
Then Tails is running from USB drive "old" 0.180
And all tps features are active 7.075
When I write some files expected to persist 1.485
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 2.222
And I take note of which tps features are available 6.857
And I shutdown Tails and wait for the computer to power off 2.588
# 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.687
After features/support/hooks.rb:339 0.406
After features/support/hooks.rb:108 0.017
Tags: @product
2:13.277
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 without a persistent partition and stopped at Tails Greeter's login screen 8.400
And I log in to a new session 11.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.675
And I plug USB drive "to_upgrade" 2.169
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.263
Then the running Tails is installed on USB drive "to_upgrade" 19.202
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 3.997
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.817
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.206
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.160
And the boot device has safe access rights 2.228
And the expected persistent files created with the old Tails version are present in the filesystem 1.155
And all persistent directories from the old Tails version have safe access rights 1.813
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:40.027
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.218
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.025
And Tor is ready 14.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.300
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.598
Given I shutdown Tails and wait for the computer to power off 8.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.950
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.605
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.252
When the network is plugged 0.030
And Tor is ready 10.437
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.920
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.513
Given I shutdown Tails and wait for the computer to power off 4.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.344
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.827
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.022
And Tor is ready 10.573
Then the Upgrader considers the system as up-to-date 0.098
# 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.354
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.299
After features/support/hooks.rb:339 0.812
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
20.024
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 7.784
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.570
After features/support/hooks.rb:339 1.062
After features/support/hooks.rb:108 0.000