Project Number Date
test_Tails_ISO_21153-zstd-iuks 6 27 Jul 2026, 11:42

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:1.520 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:15.727
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.050
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.460
When I start Tails from USB drive "old" with network unplugged 57.680
Then the boot device has safe access rights 2.819
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.850
After features/support/hooks.rb:108 0.041
Tags: @product
1:30.820
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 56.746
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 24.721
And I take note of which tps features are available 4.242
Then a Tails persistence partition exists on USB drive "old" 0.662
And I shutdown Tails and wait for the computer to power off 4.103
After features/support/hooks.rb:339 0.564
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.355
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.031
Then Tails is running from USB drive "old" 0.296
And all tps features are active 5.658
When I write some files expected to persist 1.485
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.274
And I take note of which tps features are available 4.161
And I shutdown Tails and wait for the computer to power off 4.055
# 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.769
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.906
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.348
And I log in to a new session 12.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.711
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.997
Then the running Tails is installed on USB drive "to_upgrade" 15.650
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 2.776
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.604
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.157
And all persistent directories from the old Tails version have safe access rights 1.991
After features/support/hooks.rb:339 0.877
After features/support/hooks.rb:108 0.005
3:50.264
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.028
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.369
When the network is plugged 0.014
And Tor is ready 13.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.907
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.892
Given I shutdown Tails and wait for the computer to power off 5.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.910
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.196
When the network is plugged 0.014
And Tor is ready 10.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.060
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.750
Given I shutdown Tails and wait for the computer to power off 4.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.375
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.600
And the file system changes introduced in version 6.3~testoverlayfs are present 0.382
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.015
And Tor is ready 9.919
Then the Upgrader considers the system as up-to-date 10.629
# 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.390
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.020
21.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 11.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.990
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.000