Project Number Date
test_Tails_ISO_21153-zstd-iuks 1 22 Jul 2026, 20:52

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 12:8.466 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.513
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.547
When I start Tails from USB drive "old" with network unplugged 54.511
Then the boot device has safe access rights 2.662
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:339 2.030
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.747
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.231
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 25.783
And I take note of which tps features are available 4.640
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 8.219
After features/support/hooks.rb:339 0.198
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.298
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.275
Then Tails is running from USB drive "old" 0.294
And all tps features are active 5.108
When I write some files expected to persist 1.369
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.018
And I take note of which tps features are available 3.966
And I shutdown Tails and wait for the computer to power off 8.215
# 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.457
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.008
Tags: @product
2:13.761
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 without a persistent partition and stopped at Tails Greeter's login screen 8.492
And I log in to a new session 13.596
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.002
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.304
Then the running Tails is installed on USB drive "to_upgrade" 15.868
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 2.560
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.045
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.185
Then all tps features from the old Tails version are active 1.209
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 2.696
And the expected persistent files created with the old Tails version are present in the filesystem 1.399
And all persistent directories from the old Tails version have safe access rights 2.145
After features/support/hooks.rb:339 0.671
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:51.765
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.069
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.019
And Tor is ready 13.654
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.137
Given I shutdown Tails and wait for the computer to power off 5.650
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.213
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.681
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.209
When the network is plugged 0.015
And Tor is ready 9.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.161
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.816
Given I shutdown Tails and wait for the computer to power off 4.103
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.148
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 4.660
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.012
And Tor is ready 9.992
Then the Upgrader considers the system as up-to-date 10.515
# 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 4.150
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:339 0.682
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.334
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.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.017
And Tor is ready 8.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.827
After features/support/hooks.rb:339 0.830
After features/support/hooks.rb:108 0.000