Project Number Date
test_Tails_ISO_21565-flatpak-safe 10 25 Aug 2026, 03: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:0.635 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.885
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.997
When I start Tails from USB drive "old" with network unplugged 49.191
Then the boot device has safe access rights 2.025
And Tails is running from USB drive "old" 0.183
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 1.443
After features/support/hooks.rb:108 0.004
Tags: @product
1:17.452
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 46.765
Then Tails is running from USB drive "old" 0.195
And I create a persistent partition 21.281
And I take note of which tps features are available 6.091
Then a Tails persistence partition exists on USB drive "old" 0.489
And I shutdown Tails and wait for the computer to power off 2.555
After features/support/hooks.rb:339 0.373
After features/support/hooks.rb:108 0.015
Tags: @product
1:28.874
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.048
Then Tails is running from USB drive "old" 0.183
And all tps features are active 7.031
When I write some files expected to persist 1.060
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.203
And all persistent directories from the old Tails version have safe access rights 1.731
And I take note of which tps features are available 5.856
And I shutdown Tails and wait for the computer to power off 2.505
# 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.055
After features/support/hooks.rb:339 0.466
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.358
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.197
And I log in to a new session 11.086
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.624
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.073
Then the running Tails is installed on USB drive "to_upgrade" 17.894
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.660
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.031
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.248
Then all tps features from the old Tails version are active 0.982
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.045
And the expected persistent files created with the old Tails version are present in the filesystem 0.901
And all persistent directories from the old Tails version have safe access rights 1.525
After features/support/hooks.rb:339 0.603
After features/support/hooks.rb:108 0.004
3:33.984
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.149
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.286
When the network is plugged 0.032
And Tor is ready 12.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.436
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.198
Given I shutdown Tails and wait for the computer to power off 5.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.770
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.163
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.172
When the network is plugged 0.031
And Tor is ready 9.932
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.436
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.600
Given I shutdown Tails and wait for the computer to power off 3.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.526
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.348
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.086
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.024
And Tor is ready 10.121
Then the Upgrader considers the system as up-to-date 10.377
# 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.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.292
After features/support/hooks.rb:339 0.814
After features/support/hooks.rb:108 0.044
18.049
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 7.822
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.160
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 7.934
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.006
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.000