Project Number Date
test_Tails_ISO_21565-flatpak-safe 65 04 Oct 2026, 03:30

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:11.108 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:5.018
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.952
When I start Tails from USB drive "old" with network unplugged 47.026
Then the boot device has safe access rights 2.390
And Tails is running from USB drive "old" 0.173
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.102
After features/support/hooks.rb:339 1.254
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 47.924
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.604
And I take note of which tps features are available 7.802
Then a Tails persistence partition exists on USB drive "old" 0.492
And I shutdown Tails and wait for the computer to power off 2.544
After features/support/hooks.rb:339 0.593
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.657
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.748
Then Tails is running from USB drive "old" 0.203
And all tps features are active 8.631
When I write some files expected to persist 1.094
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.648
And I take note of which tps features are available 7.229
And I shutdown Tails and wait for the computer to power off 3.900
# 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.677
After features/support/hooks.rb:339 0.146
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.472
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.214
And I log in to a new session 12.131
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.432
Then the running Tails is installed on USB drive "to_upgrade" 17.507
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.961
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.487
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.364
Then all tps features from the old Tails version are active 1.160
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.022
And the expected persistent files created with the old Tails version are present in the filesystem 0.899
And all persistent directories from the old Tails version have safe access rights 1.713
After features/support/hooks.rb:339 0.738
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:25.869
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.214
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.035
And Tor is ready 11.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.935
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.760
Given I shutdown Tails and wait for the computer to power off 5.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.389
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.678
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.158
When the network is plugged 0.040
And Tor is ready 10.525
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.732
Given I shutdown Tails and wait for the computer to power off 2.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.431
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.241
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.131
When the network is plugged 0.020
And Tor is ready 10.107
Then the Upgrader considers the system as up-to-date 0.094
# 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.424
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.894
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.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 7.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.749
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.000