Project Number Date
test_Tails_ISO_stable 6528 23 Jul 2026, 22:32

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:13.462 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
56.162
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.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.135
When I start Tails from USB drive "old" with network unplugged 38.852
Then the boot device has safe access rights 2.407
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 1.268
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.974
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 50.283
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.667
And I take note of which tps features are available 3.963
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 4.246
After features/support/hooks.rb:339 0.415
After features/support/hooks.rb:108 0.007
Tags: @product
1:29.780
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.304
Then Tails is running from USB drive "old" 0.265
And all tps features are active 4.866
When I write some files expected to persist 1.246
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 3.958
And I shutdown Tails and wait for the computer to power off 3.933
# 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.885
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.769
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 without a persistent partition and stopped at Tails Greeter's login screen 7.982
And I log in to a new session 11.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.733
Then the running Tails is installed on USB drive "to_upgrade" 14.513
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.194
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.532
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.960
Then all tps features from the old Tails version are active 1.028
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.470
And the expected persistent files created with the old Tails version are present in the filesystem 1.024
And all persistent directories from the old Tails version have safe access rights 1.752
After features/support/hooks.rb:339 0.709
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:45.510
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.835
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
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.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.016
And Tor is ready 17.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.748
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.307
Given I shutdown Tails and wait for the computer to power off 6.976
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.975
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.623
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
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.128
# 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.197
When the network is plugged 0.017
And Tor is ready 10.706
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.673
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.653
Given I shutdown Tails and wait for the computer to power off 4.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.063
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.701
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.014
And Tor is ready 10.573
Then the Upgrader considers the system as up-to-date 10.505
# 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.057
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
19.731
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.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.935
After features/support/hooks.rb:339 1.030
After features/support/hooks.rb:108 0.000