Project Number Date
test_Tails_ISO_stable 6440 11 Jun 2026, 13:39

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:34.865 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:2.843
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.710
When I start Tails from USB drive "old" with network unplugged 43.907
Then the boot device has safe access rights 3.255
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:335 3.791
After features/support/hooks.rb:104 0.012
Tags: @product
1:28.857
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 58.063
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 25.290
And I take note of which tps features are available 0.372
Then a Tails persistence partition exists on USB drive "old" 0.605
And I shutdown Tails and wait for the computer to power off 4.171
After features/support/hooks.rb:335 0.487
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.726
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.692
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.193
When I write some files expected to persist 1.334
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 2.129
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.053
# 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.324
After features/support/hooks.rb:335 0.118
After features/support/hooks.rb:104 0.008
Tags: @product
2:12.516
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.087
And I log in to a new session 12.347
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.756
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.040
Then the running Tails is installed on USB drive "to_upgrade" 16.765
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:335 2.153
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.654
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.892
Then all tps features from the old Tails version are active 0.947
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.467
And the expected persistent files created with the old Tails version are present in the filesystem 1.181
And all persistent directories from the old Tails version have safe access rights 1.860
After features/support/hooks.rb:335 0.628
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:46.958
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.643
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.018
And Tor is ready 12.533
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.673
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.393
Given I shutdown Tails and wait for the computer to power off 6.854
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.168
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.387
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.217
When the network is plugged 0.017
And Tor is ready 10.231
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.755
Given I shutdown Tails and wait for the computer to power off 4.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.643
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.281
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.245
When the network is plugged 0.018
And Tor is ready 12.377
Then the Upgrader considers the system as up-to-date 10.634
# 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.744
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.500
After features/support/hooks.rb:335 1.020
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
22.308
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.995
After features/support/hooks.rb:335 0.962
After features/support/hooks.rb:104 0.000