Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 37 21 May 2026, 15:33

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:41.488 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:20.012
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.822
When I start Tails from USB drive "old" with network unplugged 1:1.740
Then the boot device has safe access rights 2.598
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:335 1.664
After features/support/hooks.rb:104 0.014
Tags: @product
1:28.897
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 55.000
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 25.522
And I take note of which tps features are available 0.424
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 6.874
After features/support/hooks.rb:335 0.516
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.857
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.655
Then Tails is running from USB drive "old" 0.232
And all tps features are active 1.104
When I write some files expected to persist 1.273
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.903
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 6.927
# 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.053
After features/support/hooks.rb:335 0.545
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.353
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.199
And I log in to a new session 13.022
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.910
And I plug USB drive "to_upgrade" 2.301
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.953
Then the running Tails is installed on USB drive "to_upgrade" 15.633
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:335 2.325
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.548
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.745
Then all tps features from the old Tails version are active 0.953
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.573
And the expected persistent files created with the old Tails version are present in the filesystem 1.233
And all persistent directories from the old Tails version have safe access rights 1.771
After features/support/hooks.rb:335 0.719
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:43.543
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 8.511
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.043
And Tor is ready 12.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.123
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.840
Given I shutdown Tails and wait for the computer to power off 6.818
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.913
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.817
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.528
Given I shutdown Tails and wait for the computer to power off 8.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.468
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.412
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.016
And Tor is ready 10.377
Then the Upgrader considers the system as up-to-date 10.585
# 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.768
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:335 1.053
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
21.274
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.514
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.051
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.042
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.381
After features/support/hooks.rb:335 0.975
After features/support/hooks.rb:104 0.000