Project Number Date
test_Tails_ISO_stable-flatpak 30 28 Sep 2026, 19:37

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:27.624 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:8.666
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.113
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.934
When I start Tails from USB drive "old" with network unplugged 50.987
Then the boot device has safe access rights 1.950
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 1.792
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.012
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login 47.701
Then Tails is running from USB drive "old" 0.188
And I create a persistent partition 24.956
And I take note of which tps features are available 6.831
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 2.625
After features/support/hooks.rb:339 0.293
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.295
Then Tails is running from USB drive "old" 0.175
And all tps features are active 7.004
When I write some files expected to persist 1.147
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 2.154
And I take note of which tps features are available 6.216
And I shutdown Tails and wait for the computer to power off 2.535
# 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.366
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.302
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.407
And I log in to a new session 13.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.610
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.348
Then the running Tails is installed on USB drive "to_upgrade" 18.344
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.831
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.242
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:2.933
Then all tps features from the old Tails version are active 1.192
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.287
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.150
After features/support/hooks.rb:339 0.982
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.608
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.070
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.027
And Tor is ready 13.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.158
Given I shutdown Tails and wait for the computer to power off 6.876
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.588
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.847
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
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.118
# 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.205
When the network is plugged 0.036
And Tor is ready 10.554
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.006
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.501
Given I shutdown Tails and wait for the computer to power off 4.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.891
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.375
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.153
When the network is plugged 0.022
And Tor is ready 10.495
Then the Upgrader considers the system as up-to-date 0.105
# 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.244
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.304
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
19.411
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.743
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.356
After features/support/hooks.rb:339 0.815
After features/support/hooks.rb:108 0.000