Project Number Date
test_Tails_ISO_21153-zstd-iuks 4 25 Jul 2026, 11:30

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:29.454 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.023
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.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.297
When I start Tails from USB drive "old" with network unplugged 53.433
Then the boot device has safe access rights 2.603
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.423
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.666
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 50.883
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.658
And I take note of which tps features are available 4.105
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 4.237
After features/support/hooks.rb:339 0.258
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.074
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.653
Then Tails is running from USB drive "old" 0.270
And all tps features are active 4.784
When I write some files expected to persist 1.204
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.298
And all persistent directories from the old Tails version have safe access rights 1.841
And I take note of which tps features are available 3.735
And I shutdown Tails and wait for the computer to power off 4.189
# 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.875
After features/support/hooks.rb:339 0.281
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.816
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.063
And I log in to a new session 13.608
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.748
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.209
Then the running Tails is installed on USB drive "to_upgrade" 14.687
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.393
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.211
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.555
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.373
And the expected persistent files created with the old Tails version are present in the filesystem 1.080
And all persistent directories from the old Tails version have safe access rights 1.891
After features/support/hooks.rb:339 0.527
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:42.116
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.694
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.014
And Tor is ready 13.205
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.863
Given I shutdown Tails and wait for the computer to power off 5.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.774
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.516
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.186
When the network is plugged 0.012
And Tor is ready 10.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.754
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.648
Given I shutdown Tails and wait for the computer to power off 4.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.597
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.891
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.018
And Tor is ready 10.542
Then the Upgrader considers the system as up-to-date 10.550
# 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.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 0.774
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.543
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.258
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.893
After features/support/hooks.rb:339 0.669
After features/support/hooks.rb:108 0.000