Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 80 01 Jul 2026, 14:42

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:38.526 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:16.676
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.558
When I start Tails from USB drive "old" with network unplugged 56.892
Then the boot device has safe access rights 3.256
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:339 1.764
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.596
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 57.911
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 25.352
And I take note of which tps features are available 4.400
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 8.011
After features/support/hooks.rb:339 0.266
After features/support/hooks.rb:108 0.006
Tags: @product
1:45.680
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.983
Then Tails is running from USB drive "old" 0.237
And all tps features are active 4.926
When I write some files expected to persist 1.372
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 2.258
And I take note of which tps features are available 4.387
And I shutdown Tails and wait for the computer to power off 8.251
# 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.720
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.466
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.515
And I log in to a new session 14.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.907
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.417
Then the running Tails is installed on USB drive "to_upgrade" 15.879
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:339 2.981
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.976
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.538
Then all tps features from the old Tails version are active 0.950
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.791
And the expected persistent files created with the old Tails version are present in the filesystem 1.349
And all persistent directories from the old Tails version have safe access rights 1.999
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:8.083
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.363
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.015
And Tor is ready 13.094
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.893
Given I shutdown Tails and wait for the computer to power off 10.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.902
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.361
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
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.170
# 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.284
When the network is plugged 0.017
And Tor is ready 11.244
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.635
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.986
Given I shutdown Tails and wait for the computer to power off 8.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.227
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.412
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.016
And Tor is ready 10.899
Then the Upgrader considers the system as up-to-date 10.493
# 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.867
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.466
After features/support/hooks.rb:339 0.932
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
21.047
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 7.403
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.333
After features/support/hooks.rb:339 0.694
After features/support/hooks.rb:108 0.000