Project Number Date
test_Tails_ISO_21751-test-cloudflare-dns-server 2 23 Sep 2026, 09:03

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:16.117 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:12.828
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.703
When I start Tails from USB drive "old" with network unplugged 54.963
Then the boot device has safe access rights 2.459
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 1.430
After features/support/hooks.rb:108 0.007
Tags: @product
1:20.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 48.941
Then Tails is running from USB drive "old" 0.212
And I create a persistent partition 22.017
And I take note of which tps features are available 5.835
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 2.652
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.087
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.814
Then Tails is running from USB drive "old" 0.191
And all tps features are active 7.174
When I write some files expected to persist 1.050
# 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.238
And all persistent directories from the old Tails version have safe access rights 1.604
And I take note of which tps features are available 5.713
And I shutdown Tails and wait for the computer to power off 2.522
# 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.519
After features/support/hooks.rb:339 0.247
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.595
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.263
And I log in to a new session 11.871
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.184
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.211
Then the running Tails is installed on USB drive "to_upgrade" 18.154
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.840
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.772
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.759
Then all tps features from the old Tails version are active 1.139
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.081
And the expected persistent files created with the old Tails version are present in the filesystem 0.981
And all persistent directories from the old Tails version have safe access rights 1.455
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:32.187
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.036
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
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.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.036
And Tor is ready 11.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.023
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.904
Given I shutdown Tails and wait for the computer to power off 6.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.664
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.533
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.180
When the network is plugged 0.032
And Tor is ready 10.094
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.885
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.205
Given I shutdown Tails and wait for the computer to power off 4.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.288
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.865
And the file system changes introduced in version 6.3~testoverlayfs are present 0.289
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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.151
When the network is plugged 0.032
And Tor is ready 10.690
Then the Upgrader considers the system as up-to-date 0.087
# 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.540
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:339 0.715
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
20.389
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.830
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.092
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.000