Project Number Date
test_Tails_ISO_stable 6497 12 Jul 2026, 11:31

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:37.384 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:8.464
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.105
When I start Tails from USB drive "old" with network unplugged 51.087
Then the boot device has safe access rights 2.472
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.216
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.010
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.509
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 23.664
And I take note of which tps features are available 3.767
Then a Tails persistence partition exists on USB drive "old" 0.610
And I shutdown Tails and wait for the computer to power off 4.160
After features/support/hooks.rb:339 0.410
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.949
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.960
Then Tails is running from USB drive "old" 0.255
And all tps features are active 4.852
When I write some files expected to persist 1.240
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.289
And all persistent directories from the old Tails version have safe access rights 1.826
And I take note of which tps features are available 3.660
And I shutdown Tails and wait for the computer to power off 7.879
# 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.734
After features/support/hooks.rb:339 0.347
After features/support/hooks.rb:108 0.016
Tags: @product
2:7.757
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.860
And I log in to a new session 11.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.795
Then the running Tails is installed on USB drive "to_upgrade" 14.363
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.925
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
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.491
Then all tps features from the old Tails version are active 0.906
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.149
And all persistent directories from the old Tails version have safe access rights 2.012
After features/support/hooks.rb:339 1.011
After features/support/hooks.rb:108 0.038
Tags: @product @automatic_upgrade
3:50.557
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 8.253
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.014
And Tor is ready 12.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.924
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.405
Given I shutdown Tails and wait for the computer to power off 9.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.033
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.328
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.189
When the network is plugged 0.014
And Tor is ready 11.112
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.284
Given I shutdown Tails and wait for the computer to power off 7.915
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.520
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.860
And the file system changes introduced in version 6.3~testoverlayfs are present 0.348
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.212
When the network is plugged 0.016
And Tor is ready 10.953
Then the Upgrader considers the system as up-to-date 10.529
# 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 3.803
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:339 0.926
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.419
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.249
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.672
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.165
After features/support/hooks.rb:339 0.793
After features/support/hooks.rb:108 0.000