Project Number Date
test_Tails_ISO_stable 6506 15 Jul 2026, 07:41

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:57.188 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.408
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.545
When I start Tails from USB drive "old" with network unplugged 48.845
Then the boot device has safe access rights 3.157
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:339 1.322
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 54.936
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 24.925
And I take note of which tps features are available 3.890
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 8.149
After features/support/hooks.rb:339 0.579
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.205
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 "old" with network unplugged and I login with persistence enabled 1:5.793
Then Tails is running from USB drive "old" 0.280
And all tps features are active 5.493
When I write some files expected to persist 1.419
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.029
And I take note of which tps features are available 4.478
And I shutdown Tails and wait for the computer to power off 4.144
# 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.992
After features/support/hooks.rb:339 0.089
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.765
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 8.081
And I log in to a new session 12.402
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.759
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.039
Then the running Tails is installed on USB drive "to_upgrade" 14.961
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.148
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.934
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.114
Then all tps features from the old Tails version are active 0.930
And Tails is running from USB drive "to_upgrade" 0.193
And the boot device has safe access rights 2.595
And the expected persistent files created with the old Tails version are present in the filesystem 1.186
And all persistent directories from the old Tails version have safe access rights 1.855
After features/support/hooks.rb:339 0.763
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:58.696
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.976
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.014
And Tor is ready 12.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.865
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.768
Given I shutdown Tails and wait for the computer to power off 9.478
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.593
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.787
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.210
When the network is plugged 0.012
And Tor is ready 11.912
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.452
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.883
Given I shutdown Tails and wait for the computer to power off 8.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.135
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.014
And Tor is ready 11.922
Then the Upgrader considers the system as up-to-date 10.553
# 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.292
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.319
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.317
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.000