Project Number Date
test_Tails_ISO_stable 6368 11 May 2026, 20:26

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 13:3.128 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:7.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 14.567
When I start Tails from USB drive "old" with network unplugged 47.867
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 1.430
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.904
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 57.717
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 28.038
And I take note of which tps features are available 0.888
Then a Tails persistence partition exists on USB drive "old" 0.612
And I shutdown Tails and wait for the computer to power off 7.251
After features/support/hooks.rb:331 0.505
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.196
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.162
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.525
And all persistent directories from the old Tails version have safe access rights 2.142
And I take note of which tps features are available 0.217
And I shutdown Tails and wait for the computer to power off 6.989
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.492
After features/support/hooks.rb:331 0.351
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.850
And I log in to a new session 13.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.572
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.656
Then the running Tails is installed on USB drive "to_upgrade" 18.527
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.739
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.461
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.099
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 2.667
And the expected persistent files created with the old Tails version are present in the filesystem 1.088
And all persistent directories from the old Tails version have safe access rights 2.075
After features/support/hooks.rb:331 0.895
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
4:48.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.900
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.619
When the network is plugged 0.019
And Tor is ready 24.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.353
Given I shutdown Tails and wait for the computer to power off 9.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.909
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.254
When the network is plugged 0.033
And Tor is ready 21.985
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.805
Given I shutdown Tails and wait for the computer to power off 17.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.521
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.232
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.018
And Tor is ready 22.171
Then the Upgrader considers the system as up-to-date 0.117
# 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 5.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.433
After features/support/hooks.rb:331 0.681
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
26.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 0.609
After features/support/hooks.rb:100 0.000