Project Number Date
test_Tails_ISO_21565-flatpak-safe 60 30 Sep 2026, 03:17

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:16.447 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.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.237
When I start Tails from USB drive "old" with network unplugged 50.300
Then the boot device has safe access rights 2.268
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.147
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 1.175
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.165
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 47.576
Then Tails is running from USB drive "old" 0.198
And I create a persistent partition 24.321
And I take note of which tps features are available 6.586
Then a Tails persistence partition exists on USB drive "old" 0.443
And I shutdown Tails and wait for the computer to power off 3.968
After features/support/hooks.rb:339 0.134
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.591
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.750
Then Tails is running from USB drive "old" 0.270
And all tps features are active 7.522
When I write some files expected to persist 0.999
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.265
And all persistent directories from the old Tails version have safe access rights 1.803
And I take note of which tps features are available 5.996
And I shutdown Tails and wait for the computer to power off 3.994
# 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.769
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.014
Tags: @product
2:12.791
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.373
And I log in to a new session 11.406
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.179
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.330
Then the running Tails is installed on USB drive "to_upgrade" 18.632
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.739
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.014
Then all tps features from the old Tails version are active 1.156
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.023
And the expected persistent files created with the old Tails version are present in the filesystem 0.997
And all persistent directories from the old Tails version have safe access rights 1.652
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:28.216
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 with a persistent partition enabled and logged in 8.176
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.027
And Tor is ready 12.965
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.308
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.725
Given I shutdown Tails and wait for the computer to power off 5.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.783
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.442
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
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.108
# 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.203
When the network is plugged 0.032
And Tor is ready 10.833
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.525
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.444
Given I shutdown Tails and wait for the computer to power off 2.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.566
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.577
And the file system changes introduced in version 6.3~testoverlayfs are present 0.319
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.035
And Tor is ready 10.801
Then the Upgrader considers the system as up-to-date 0.075
# 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.435
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.066
Tags: @product @automatic_upgrade
20.038
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.032
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.216
After features/support/hooks.rb:339 0.660
After features/support/hooks.rb:108 0.000