Project Number Date
test_Tails_ISO_21565-flatpak-safe 123 04 Nov 2026, 21:09

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:47.986 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:19.836
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.128
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 14.992
When I start Tails from USB drive "old" with network unplugged 1:0.453
Then the boot device has safe access rights 2.597
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.149
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 3.704
After features/support/hooks.rb:108 0.057
Tags: @product
1:25.539
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 50.372
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.344
And I take note of which tps features are available 6.483
Then a Tails persistence partition exists on USB drive "old" 0.592
And I shutdown Tails and wait for the computer to power off 4.457
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.005
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.100
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.371
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.461
When I write some files expected to persist 0.985
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.313
And all persistent directories from the old Tails version have safe access rights 1.881
And I take note of which tps features are available 6.555
And I shutdown Tails and wait for the computer to power off 4.420
# 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.691
After features/support/hooks.rb:339 0.214
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.325
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 9.171
And I log in to a new session 12.092
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.911
Then the running Tails is installed on USB drive "to_upgrade" 18.617
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.718
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.708
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.993
Then all tps features from the old Tails version are active 1.232
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.776
And the expected persistent files created with the old Tails version are present in the filesystem 1.295
And all persistent directories from the old Tails version have safe access rights 2.062
After features/support/hooks.rb:339 0.645
After features/support/hooks.rb:108 0.014
3:41.611
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.458
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.046
And Tor is ready 13.084
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.110
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.394
Given I shutdown Tails and wait for the computer to power off 5.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.778
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.222
And the file system changes introduced in version 6.2~testoverlayfs are present 0.173
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.179
When the network is plugged 0.033
And Tor is ready 10.513
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.331
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.679
Given I shutdown Tails and wait for the computer to power off 2.649
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.825
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.271
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.084
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.037
And Tor is ready 10.451
Then the Upgrader considers the system as up-to-date 0.120
# 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.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:339 0.733
After features/support/hooks.rb:108 0.020
18.817
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.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
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.027
And Tor is ready 8.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.491
After features/support/hooks.rb:339 0.853
After features/support/hooks.rb:108 0.000