Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 74 26 Jun 2026, 14:25

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:36.504 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.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.181
When I start Tails from USB drive "old" with network unplugged 57.479
Then the boot device has safe access rights 2.483
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.770
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 51.554
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 23.500
And I take note of which tps features are available 3.641
Then a Tails persistence partition exists on USB drive "old" 0.502
And I shutdown Tails and wait for the computer to power off 8.143
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.591
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.973
Then Tails is running from USB drive "old" 0.246
And all tps features are active 4.618
When I write some files expected to persist 1.177
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.782
And I take note of which tps features are available 3.678
And I shutdown Tails and wait for the computer to power off 8.071
# 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.514
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
2:7.701
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.199
And I log in to a new session 10.442
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.787
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.049
Then the running Tails is installed on USB drive "to_upgrade" 14.692
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 0.689
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.434
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.125
Then all tps features from the old Tails version are active 0.905
And Tails is running from USB drive "to_upgrade" 0.194
And the boot device has safe access rights 2.191
And the expected persistent files created with the old Tails version are present in the filesystem 1.099
And all persistent directories from the old Tails version have safe access rights 1.865
After features/support/hooks.rb:339 0.829
After features/support/hooks.rb:108 0.005
3:42.909
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 7.883
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.015
And Tor is ready 12.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.892
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.605
Given I shutdown Tails and wait for the computer to power off 9.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.468
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 5.173
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.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.198
When the network is plugged 0.013
And Tor is ready 9.560
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.003
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.243
Given I shutdown Tails and wait for the computer to power off 4.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.345
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.507
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.015
And Tor is ready 9.919
Then the Upgrader considers the system as up-to-date 10.539
# 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.862
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:339 1.118
After features/support/hooks.rb:108 0.009
19.390
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 7.282
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.040
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 8.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.139
After features/support/hooks.rb:339 0.831
After features/support/hooks.rb:108 0.000