Project Number Date
test_Tails_ISO_21565-flatpak-safe 76 06 Oct 2026, 19:55

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.789 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.878
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.875
When I start Tails from USB drive "old" with network unplugged 54.305
Then the boot device has safe access rights 2.736
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:339 1.350
After features/support/hooks.rb:108 0.025
Tags: @product
1:25.805
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login 49.743
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.549
And I take note of which tps features are available 6.731
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 3.925
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.054
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.702
Then Tails is running from USB drive "old" 0.221
And all tps features are active 8.666
When I write some files expected to persist 1.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 1.672
And I take note of which tps features are available 6.669
And I shutdown Tails and wait for the computer to power off 2.553
# 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.735
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.586
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.630
And I log in to a new session 12.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.798
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.203
Then the running Tails is installed on USB drive "to_upgrade" 18.676
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.788
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.663
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.323
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.425
And the expected persistent files created with the old Tails version are present in the filesystem 0.979
And all persistent directories from the old Tails version have safe access rights 1.559
After features/support/hooks.rb:339 0.513
After features/support/hooks.rb:108 0.006
3:46.163
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 8.632
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.031
And Tor is ready 13.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.316
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.030
Given I shutdown Tails and wait for the computer to power off 5.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.905
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 8.722
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.220
When the network is plugged 0.032
And Tor is ready 10.703
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.459
Given I shutdown Tails and wait for the computer to power off 4.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.865
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.438
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.023
And Tor is ready 15.728
Then the Upgrader considers the system as up-to-date 0.127
# 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.675
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.009
20.637
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.182
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 11.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.000