Project Number Date
test_Tails_ISO_21153-zstd-iuks 3 24 Jul 2026, 11:41

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:4.886 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:16.530
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.842
When I start Tails from USB drive "old" with network unplugged 58.162
Then the boot device has safe access rights 2.778
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.882
After features/support/hooks.rb:108 0.007
Tags: @product
1:29.989
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 55.362
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 25.353
And I take note of which tps features are available 4.233
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 4.151
After features/support/hooks.rb:339 0.409
After features/support/hooks.rb:108 0.008
Tags: @product
1:36.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.958
Then Tails is running from USB drive "old" 0.242
And all tps features are active 4.751
When I write some files expected to persist 1.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 2.335
And I take note of which tps features are available 4.502
And I shutdown Tails and wait for the computer to power off 4.344
# 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.051
After features/support/hooks.rb:339 0.284
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.902
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.472
And I log in to a new session 14.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.809
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.558
Then the running Tails is installed on USB drive "to_upgrade" 16.258
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 2.460
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.991
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.714
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 1.816
After features/support/hooks.rb:339 0.602
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
3:53.463
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.252
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.029
And Tor is ready 13.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.387
Given I shutdown Tails and wait for the computer to power off 7.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.608
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.464
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.242
When the network is plugged 0.018
And Tor is ready 11.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.792
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.412
Given I shutdown Tails and wait for the computer to power off 4.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.947
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.220
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.014
And Tor is ready 11.053
Then the Upgrader considers the system as up-to-date 10.625
# 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.465
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:339 1.028
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
20.744
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.485
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.128
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.765
After features/support/hooks.rb:339 0.989
After features/support/hooks.rb:108 0.000