Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 62 14 Jun 2026, 14:22

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:47.576 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.612
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 12.800
When I start Tails from USB drive "old" with network unplugged 1:3.098
Then the boot device has safe access rights 2.811
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 1.591
After features/support/hooks.rb:108 0.017
Tags: @product
1:30.898
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login 53.864
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 24.174
And I take note of which tps features are available 3.975
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 7.996
After features/support/hooks.rb:339 0.496
After features/support/hooks.rb:108 0.017
Tags: @product
1:34.380
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.417
Then Tails is running from USB drive "old" 0.233
And all tps features are active 5.088
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.942
And I take note of which tps features are available 3.630
And I shutdown Tails and wait for the computer to power off 8.257
# 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.965
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.017
Tags: @product
2:7.382
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 7.552
And I log in to a new session 11.919
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.691
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.045
Then the running Tails is installed on USB drive "to_upgrade" 13.673
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.109
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.144
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.137
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.568
Then all tps features from the old Tails version are active 0.907
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.490
And the expected persistent files created with the old Tails version are present in the filesystem 1.006
And all persistent directories from the old Tails version have safe access rights 1.793
After features/support/hooks.rb:339 0.621
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
3:44.616
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.966
And no SquashFS delta is installed 0.068
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.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.016
And Tor is ready 13.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.908
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.823
Given I shutdown Tails and wait for the computer to power off 9.693
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.208
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.747
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
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.164
# 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.188
When the network is plugged 0.016
And Tor is ready 9.665
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.246
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.479
Given I shutdown Tails and wait for the computer to power off 4.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.863
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.570
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.017
And Tor is ready 10.638
Then the Upgrader considers the system as up-to-date 10.533
# 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.753
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.354
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
19.540
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 7.795
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
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.059
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.548
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.867
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.000