Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 5 30 Apr 2026, 14:41

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:37.845 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:3.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.072
When I start Tails from USB drive "old" with network unplugged 44.996
Then the boot device has safe access rights 2.723
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.496
After features/support/hooks.rb:100 0.011
Tags: @product
1:27.718
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 56.189
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 25.287
And I take note of which tps features are available 0.900
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 4.418
After features/support/hooks.rb:331 0.160
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.238
Then Tails is running from USB drive "old" 0.237
And all tps features are active 1.137
When I write some files expected to persist 1.284
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.127
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.571
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.192
After features/support/hooks.rb:331 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.429
And I log in to a new session 13.482
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.023
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.975
Then the running Tails is installed on USB drive "to_upgrade" 16.375
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.113
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.158
Then all tps features from the old Tails version are active 1.019
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 2.840
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 1.961
After features/support/hooks.rb:331 0.564
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:42.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.344
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
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.364
When the network is plugged 0.018
And Tor is ready 23.275
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.151
Given I shutdown Tails and wait for the computer to power off 19.044
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.821
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.417
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.221
When the network is plugged 0.018
And Tor is ready 20.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.743
Given I shutdown Tails and wait for the computer to power off 17.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.867
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.387
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.032
And Tor is ready 22.352
Then the Upgrader considers the system as up-to-date 0.119
# 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.914
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:331 0.800
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
27.515
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.516
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 19.169
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.468
After features/support/hooks.rb:331 0.839
After features/support/hooks.rb:100 0.000