Project Number Date
test_Tails_ISO_stable 6618 01 Sep 2026, 07:30

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:40.608 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:4.033
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 15.043
When I start Tails from USB drive "old" with network unplugged 44.669
Then the boot device has safe access rights 2.486
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.491
After features/support/hooks.rb:108 0.030
Tags: @product
1:27.779
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 50.780
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.948
And I take note of which tps features are available 7.760
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 4.441
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.738
Then Tails is running from USB drive "old" 0.216
And all tps features are active 7.114
When I write some files expected to persist 1.182
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 1.867
And I take note of which tps features are available 6.799
And I shutdown Tails and wait for the computer to power off 2.643
# 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" 12.024
After features/support/hooks.rb:339 0.123
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.812
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 without a persistent partition and stopped at Tails Greeter's login screen 8.723
And I log in to a new session 13.615
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.889
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.760
Then the running Tails is installed on USB drive "to_upgrade" 18.299
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 1.991
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.484
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.817
Then all tps features from the old Tails version are active 1.197
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.665
And the expected persistent files created with the old Tails version are present in the filesystem 1.381
And all persistent directories from the old Tails version have safe access rights 2.048
After features/support/hooks.rb:339 0.808
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:44.855
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 with a persistent partition enabled and logged in 8.154
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.038
And Tor is ready 14.509
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.327
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.444
Given I shutdown Tails and wait for the computer to power off 5.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.575
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.133
When the network is plugged 0.032
And Tor is ready 10.340
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.004
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.450
Given I shutdown Tails and wait for the computer to power off 4.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.398
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.331
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.026
And Tor is ready 10.616
Then the Upgrader considers the system as up-to-date 10.449
# 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.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.436
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.937
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
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.050
And Tor is ready 9.516
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.648
After features/support/hooks.rb:339 0.723
After features/support/hooks.rb:108 0.000