Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 59 12 Jun 2026, 12:53

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:23.037 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:19.202
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.705
When I start Tails from USB drive "old" with network unplugged 1:0.757
Then the boot device has safe access rights 2.817
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:339 1.323
After features/support/hooks.rb:108 0.014
Tags: @product
1:35.892
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 55.961
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 26.194
And I take note of which tps features are available 4.564
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 8.302
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.015
Tags: @product
1:37.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.953
Then Tails is running from USB drive "old" 0.228
And all tps features are active 5.989
When I write some files expected to persist 1.326
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 2.011
And I take note of which tps features are available 3.860
And I shutdown Tails and wait for the computer to power off 6.886
# 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.806
After features/support/hooks.rb:339 0.278
After features/support/hooks.rb:108 0.015
Tags: @product
2:12.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.012
And I log in to a new session 13.007
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.734
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.194
Then the running Tails is installed on USB drive "to_upgrade" 16.199
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 2.333
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.386
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.711
Then all tps features from the old Tails version are active 1.038
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 2.189
After features/support/hooks.rb:339 0.909
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
4:1.554
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.548
And no SquashFS delta is installed 0.059
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.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.016
And Tor is ready 12.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.271
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.283
Given I shutdown Tails and wait for the computer to power off 9.745
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.773
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.852
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.204
When the network is plugged 0.018
And Tor is ready 10.208
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.494
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.774
Given I shutdown Tails and wait for the computer to power off 8.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.735
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.157
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.014
And Tor is ready 10.206
Then the Upgrader considers the system as up-to-date 10.550
# 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.478
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.488
After features/support/hooks.rb:339 0.926
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
21.693
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.095
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.000