Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 32 19 May 2026, 14:39

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:51.659 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:11.364
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.671
When I start Tails from USB drive "old" with network unplugged 53.189
Then the boot device has safe access rights 2.644
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:335 1.543
After features/support/hooks.rb:104 0.028
Tags: @product
1:34.697
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 59.287
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 26.864
And I take note of which tps features are available 0.424
Then a Tails persistence partition exists on USB drive "old" 0.654
And I shutdown Tails and wait for the computer to power off 7.141
After features/support/hooks.rb:335 0.249
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.941
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.956
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.344
When I write some files expected to persist 1.306
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 2.261
And I take note of which tps features are available 0.271
And I shutdown Tails and wait for the computer to power off 8.430
# 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.521
After features/support/hooks.rb:335 0.368
After features/support/hooks.rb:104 0.009
Tags: @product
2:16.650
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.487
And I log in to a new session 14.796
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.979
And I plug USB drive "to_upgrade" 2.877
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.645
Then the running Tails is installed on USB drive "to_upgrade" 16.528
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:335 2.869
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.948
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.514
Then all tps features from the old Tails version are active 1.132
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.680
And the expected persistent files created with the old Tails version are present in the filesystem 1.127
And all persistent directories from the old Tails version have safe access rights 2.064
After features/support/hooks.rb:335 0.831
After features/support/hooks.rb:104 0.020
Tags: @product @automatic_upgrade
4:15.017
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.469
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.017
And Tor is ready 12.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 28.057
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.774
Given I shutdown Tails and wait for the computer to power off 11.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.028
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.371
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.253
When the network is plugged 0.015
And Tor is ready 10.363
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.787
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.369
Given I shutdown Tails and wait for the computer to power off 7.501
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.679
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.207
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.018
And Tor is ready 11.827
Then the Upgrader considers the system as up-to-date 0.113
# 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 5.001
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:335 0.988
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
50.039
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.495
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.150
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 13.147
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 28.806
After features/support/hooks.rb:335 1.239
After features/support/hooks.rb:104 0.000