Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 69 21 Jun 2026, 14:32

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:12.800 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:14.971
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 13.280
When I start Tails from USB drive "old" with network unplugged 56.928
Then the boot device has safe access rights 2.809
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:339 3.804
After features/support/hooks.rb:108 0.023
Tags: @product
1:34.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.135
And I start Tails from USB drive "old" with network unplugged and I login 55.690
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 25.279
And I take note of which tps features are available 4.425
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:339 0.461
After features/support/hooks.rb:108 0.021
Tags: @product
1:35.491
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.129
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.399
Then Tails is running from USB drive "old" 0.259
And all tps features are active 4.883
When I write some files expected to persist 1.256
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.920
And I take note of which tps features are available 3.879
And I shutdown Tails and wait for the computer to power off 3.003
# 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" 12.320
After features/support/hooks.rb:339 0.424
After features/support/hooks.rb:108 0.025
Tags: @product
2:12.584
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.892
And I log in to a new session 12.601
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.460
Then the running Tails is installed on USB drive "to_upgrade" 15.330
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.452
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.945
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.159
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.119
Then all tps features from the old Tails version are active 1.023
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.772
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.227
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
3:59.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.201
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.016
And Tor is ready 12.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.058
Given I shutdown Tails and wait for the computer to power off 8.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.497
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.140
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.174
# 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.311
When the network is plugged 0.018
And Tor is ready 10.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.943
Given I shutdown Tails and wait for the computer to power off 7.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.100
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.016
And Tor is ready 10.803
Then the Upgrader considers the system as up-to-date 10.594
# 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.825
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
21.060
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.882
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.029
After features/support/hooks.rb:339 0.731
After features/support/hooks.rb:108 0.000