Project Number Date
test_Tails_ISO_stable 6726 07 Oct 2026, 07:53

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:3.882 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:14.939
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 13.936
When I start Tails from USB drive "old" with network unplugged 56.357
Then the boot device has safe access rights 2.642
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.995
After features/support/hooks.rb:108 0.010
Tags: @product
1:31.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 1.580
And I start Tails from USB drive "old" with network unplugged and I login 49.638
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 24.897
And I take note of which tps features are available 9.942
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 4.364
After features/support/hooks.rb:339 0.583
After features/support/hooks.rb:108 0.013
Tags: @product
1:41.600
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.378
Then Tails is running from USB drive "old" 0.278
And all tps features are active 7.311
When I write some files expected to persist 1.168
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.923
And I take note of which tps features are available 7.002
And I shutdown Tails and wait for the computer to power off 4.341
# 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" 13.613
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.010
Tags: @product
2:15.878
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.046
And I log in to a new session 11.447
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.954
And I plug USB drive "to_upgrade" 2.178
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.744
Then the running Tails is installed on USB drive "to_upgrade" 20.236
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.100
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.124
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.642
Then all tps features from the old Tails version are active 1.264
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.713
And the expected persistent files created with the old Tails version are present in the filesystem 1.053
And all persistent directories from the old Tails version have safe access rights 1.824
After features/support/hooks.rb:339 0.747
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:46.922
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.657
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.027
And Tor is ready 13.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.007
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.123
Given I shutdown Tails and wait for the computer to power off 5.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.259
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.871
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.154
When the network is plugged 0.032
And Tor is ready 10.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.373
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.288
Given I shutdown Tails and wait for the computer to power off 3.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.268
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 9.384
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.033
And Tor is ready 10.978
Then the Upgrader considers the system as up-to-date 0.095
# 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.008
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.758
After features/support/hooks.rb:339 1.140
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
21.319
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.810
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.060
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.765
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.000