Project Number Date
test_Tails_ISO_stable-flatpak 5 08 Sep 2026, 18: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:7.066 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:5.914
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.637
When I start Tails from USB drive "old" with network unplugged 48.478
Then the boot device has safe access rights 1.997
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.624
After features/support/hooks.rb:108 0.015
Tags: @product
1:31.274
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 52.622
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 26.623
And I take note of which tps features are available 7.032
Then a Tails persistence partition exists on USB drive "old" 0.639
And I shutdown Tails and wait for the computer to power off 4.058
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.578
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.148
Then Tails is running from USB drive "old" 0.207
And all tps features are active 8.233
When I write some files expected to persist 1.688
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.477
And I take note of which tps features are available 6.580
And I shutdown Tails and wait for the computer to power off 2.888
# 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.589
After features/support/hooks.rb:339 0.232
After features/support/hooks.rb:108 0.009
Tags: @product
2:14.175
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.603
And I log in to a new session 11.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.666
And I plug USB drive "to_upgrade" 2.196
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.359
Then the running Tails is installed on USB drive "to_upgrade" 19.153
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.701
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.396
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.511
Then all tps features from the old Tails version are active 1.179
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.583
And the expected persistent files created with the old Tails version are present in the filesystem 1.321
And all persistent directories from the old Tails version have safe access rights 2.486
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
4:2.880
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.411
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.288
When the network is plugged 0.025
And Tor is ready 11.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.036
Given I shutdown Tails and wait for the computer to power off 8.169
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.975
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.796
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.239
When the network is plugged 0.033
And Tor is ready 10.695
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.917
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:10.271
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 7.933
And the file system changes introduced in version 6.3~testoverlayfs are present 0.345
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.024
And Tor is ready 10.697
Then the Upgrader considers the system as up-to-date 10.473
# 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.696
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 0.970
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.845
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 with a persistent partition enabled and logged in 8.377
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.928
After features/support/hooks.rb:339 0.891
After features/support/hooks.rb:108 0.000