Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 84 07 Jul 2026, 14:29

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:48.145 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:7.658
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.965
When I start Tails from USB drive "old" with network unplugged 50.181
Then the boot device has safe access rights 2.686
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.509
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.549
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.463
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.313
And I take note of which tps features are available 4.108
Then a Tails persistence partition exists on USB drive "old" 0.636
And I shutdown Tails and wait for the computer to power off 2.741
After features/support/hooks.rb:339 0.346
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.147
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.687
Then Tails is running from USB drive "old" 0.239
And all tps features are active 5.146
When I write some files expected to persist 1.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.111
And I take note of which tps features are available 3.632
And I shutdown Tails and wait for the computer to power off 7.923
# 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.515
After features/support/hooks.rb:339 0.295
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.365
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 without a persistent partition and stopped at Tails Greeter's login screen 8.020
And I log in to a new session 12.609
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.755
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.713
Then the running Tails is installed on USB drive "to_upgrade" 14.748
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:339 2.455
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.450
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.772
Then all tps features from the old Tails version are active 1.035
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.506
And the expected persistent files created with the old Tails version are present in the filesystem 1.060
And all persistent directories from the old Tails version have safe access rights 1.743
After features/support/hooks.rb:339 0.785
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:57.106
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 7.906
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.014
And Tor is ready 12.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.521
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.678
Given I shutdown Tails and wait for the computer to power off 5.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.310
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.014
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.230
When the network is plugged 0.022
And Tor is ready 9.631
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.960
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.817
Given I shutdown Tails and wait for the computer to power off 8.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.801
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.745
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.017
And Tor is ready 21.537
Then the Upgrader considers the system as up-to-date 10.528
# 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.301
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.859
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.865
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 7.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
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.061
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 8.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.708
After features/support/hooks.rb:339 0.849
After features/support/hooks.rb:108 0.000