Project Number Date
test_Tails_ISO_21565-flatpak-safe 52 26 Sep 2026, 03:39

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 15:7.246 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:11.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.132
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.374
When I start Tails from USB drive "old" with network unplugged 54.989
Then the boot device has safe access rights 1.850
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.688
After features/support/hooks.rb:108 0.054
Tags: @product
1:17.648
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 46.203
Then Tails is running from USB drive "old" 0.169
And I create a persistent partition 22.124
And I take note of which tps features are available 6.052
Then a Tails persistence partition exists on USB drive "old" 0.466
And I shutdown Tails and wait for the computer to power off 2.553
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.401
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.398
Then Tails is running from USB drive "old" 0.161
And all tps features are active 7.008
When I write some files expected to persist 1.125
# 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.275
And all persistent directories from the old Tails version have safe access rights 1.575
And I take note of which tps features are available 5.905
And I shutdown Tails and wait for the computer to power off 2.490
# 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.255
After features/support/hooks.rb:339 0.398
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.698
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.414
And I log in to a new session 11.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.558
And I plug USB drive "to_upgrade" 2.306
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.964
Then the running Tails is installed on USB drive "to_upgrade" 17.495
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.242
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.159
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.453
Then all tps features from the old Tails version are active 1.006
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 2.199
And the expected persistent files created with the old Tails version are present in the filesystem 0.861
And all persistent directories from the old Tails version have safe access rights 1.369
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.005
7:31.200
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.198
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.151
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.036
And Tor is ready 12.219
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:13.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.216
Given I shutdown Tails and wait for the computer to power off 5.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.057
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.148
When the network is plugged 0.024
And Tor is ready 10.129
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2:3.086
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.282
Given I shutdown Tails and wait for the computer to power off 2.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.056
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.025
And Tor is ready 10.157
Then the Upgrader considers the system as up-to-date 0.074
# 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.080
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.024
21.241
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.770
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 10.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.419
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.000