Project Number Date
test_Tails_ISO_stable 6684 20 Sep 2026, 11:28

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:6.028 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:9.735
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.865
When I start Tails from USB drive "old" with network unplugged 53.507
Then the boot device has safe access rights 1.756
And Tails is running from USB drive "old" 0.157
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.134
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.692
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 45.876
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 22.640
And I take note of which tps features are available 6.240
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 2.532
After features/support/hooks.rb:339 0.262
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.519
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.306
Then Tails is running from USB drive "old" 0.224
And all tps features are active 6.554
When I write some files expected to persist 0.949
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.215
And all persistent directories from the old Tails version have safe access rights 1.655
And I take note of which tps features are available 5.896
And I shutdown Tails and wait for the computer to power off 2.527
# 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" 10.977
After features/support/hooks.rb:339 0.315
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.937
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.268
And I log in to a new session 12.221
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.173
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.641
Then the running Tails is installed on USB drive "to_upgrade" 17.646
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.602
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.892
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 1:0.329
Then all tps features from the old Tails version are active 0.989
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 1.979
And the expected persistent files created with the old Tails version are present in the filesystem 0.805
And all persistent directories from the old Tails version have safe access rights 1.516
After features/support/hooks.rb:339 0.718
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:33.937
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.064
And no SquashFS delta is installed 0.053
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.075
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.311
When the network is plugged 0.036
And Tor is ready 11.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.019
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.676
Given I shutdown Tails and wait for the computer to power off 5.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.265
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.946
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.070
# 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.033
And Tor is ready 10.079
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.989
Given I shutdown Tails and wait for the computer to power off 4.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.282
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 7.401
And the file system changes introduced in version 6.3~testoverlayfs are present 0.295
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.073
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.035
And Tor is ready 10.009
Then the Upgrader considers the system as up-to-date 10.412
# 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.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
17.963
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.732
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 8.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.880
After features/support/hooks.rb:339 0.709
After features/support/hooks.rb:108 0.000