Project Number Date
test_Tails_ISO_21565-flatpak-safe 57 28 Sep 2026, 18:54

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.415 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.085
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.675
When I start Tails from USB drive "old" with network unplugged 48.547
Then the boot device has safe access rights 2.168
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.157
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 1.566
After features/support/hooks.rb:108 0.007
Tags: @product
1:26.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 52.574
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 22.619
And I take note of which tps features are available 6.441
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 4.335
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.147
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.182
Then Tails is running from USB drive "old" 0.264
And all tps features are active 7.246
When I write some files expected to persist 1.306
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.829
And I take note of which tps features are available 6.985
And I shutdown Tails and wait for the computer to power off 4.123
# 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.662
After features/support/hooks.rb:339 0.208
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.245
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 8.765
And I log in to a new session 13.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.298
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.122
Then the running Tails is installed on USB drive "to_upgrade" 18.730
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 2.186
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.116
Then all tps features from the old Tails version are active 1.135
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.226
And all persistent directories from the old Tails version have safe access rights 1.849
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.071
Tags: @product @automatic_upgrade
3:36.346
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.219
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.317
When the network is plugged 0.025
And Tor is ready 11.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.030
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.049
Given I shutdown Tails and wait for the computer to power off 5.806
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.177
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.024
And the file system changes introduced in version 6.2~testoverlayfs are present 0.186
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.029
And Tor is ready 10.536
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.306
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.593
Given I shutdown Tails and wait for the computer to power off 4.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.427
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.328
And the file system changes introduced in version 6.3~testoverlayfs are present 0.273
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.029
And Tor is ready 10.579
Then the Upgrader considers the system as up-to-date 0.066
# 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.596
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 1.045
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
19.048
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.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 10.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.293
After features/support/hooks.rb:339 0.663
After features/support/hooks.rb:108 0.000