Project Number Date
test_Tails_ISO_21751-test-cloudflare-dns-server 1 22 Sep 2026, 14:52

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:32.189 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:21.738
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.252
When I start Tails from USB drive "old" with network unplugged 1:4.422
Then the boot device has safe access rights 2.347
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.826
After features/support/hooks.rb:108 0.038
Tags: @product
1:22.404
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 47.583
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 23.052
And I take note of which tps features are available 6.807
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 4.121
After features/support/hooks.rb:339 0.440
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.658
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.161
Then Tails is running from USB drive "old" 0.189
And all tps features are active 8.087
When I write some files expected to persist 1.127
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.618
And I take note of which tps features are available 7.016
And I shutdown Tails and wait for the computer to power off 2.505
# 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.458
After features/support/hooks.rb:339 0.164
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.747
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.372
And I log in to a new session 10.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.860
And I plug USB drive "to_upgrade" 2.800
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.011
Then the running Tails is installed on USB drive "to_upgrade" 18.621
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 2.041
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.119
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.974
Then all tps features from the old Tails version are active 1.174
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.391
And the expected persistent files created with the old Tails version are present in the filesystem 1.229
And all persistent directories from the old Tails version have safe access rights 1.830
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.470
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 8.170
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.033
And Tor is ready 12.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.661
Given I shutdown Tails and wait for the computer to power off 5.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.907
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.717
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.195
When the network is plugged 0.025
And Tor is ready 10.581
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.005
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.375
Given I shutdown Tails and wait for the computer to power off 2.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.596
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.673
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.037
And Tor is ready 10.253
Then the Upgrader considers the system as up-to-date 0.085
# 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.532
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.874
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
19.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.903
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.034
And Tor is ready 8.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.240
After features/support/hooks.rb:339 0.976
After features/support/hooks.rb:108 0.000