Project Number Date
test_Tails_ISO_stable 6606 26 Aug 2026, 11:38

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:46.789 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:9.541
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.399
When I start Tails from USB drive "old" with network unplugged 52.459
Then the boot device has safe access rights 1.940
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.705
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.892
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 49.348
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 22.521
And I take note of which tps features are available 6.510
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 2.643
After features/support/hooks.rb:339 0.430
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.710
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.945
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.962
When I write some files expected to persist 1.078
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.119
And all persistence configuration files have safe access rights 0.208
And all persistent directories from the old Tails version have safe access rights 1.510
And I take note of which tps features are available 6.454
And I shutdown Tails and wait for the computer to power off 3.970
# 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.158
After features/support/hooks.rb:339 0.107
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.554
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.694
And I log in to a new session 11.509
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.744
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.238
Then the running Tails is installed on USB drive "to_upgrade" 20.867
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 3.573
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.312
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.382
Then all tps features from the old Tails version are active 1.063
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.495
And the expected persistent files created with the old Tails version are present in the filesystem 1.116
And all persistent directories from the old Tails version have safe access rights 1.894
After features/support/hooks.rb:339 0.992
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:52.832
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.625
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.026
And Tor is ready 12.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.743
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.999
Given I shutdown Tails and wait for the computer to power off 5.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.215
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.186
When the network is plugged 0.031
And Tor is ready 10.782
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.001
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.887
Given I shutdown Tails and wait for the computer to power off 4.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.258
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.573
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.042
And Tor is ready 10.592
Then the Upgrader considers the system as up-to-date 10.455
# 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.509
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.333
After features/support/hooks.rb:339 1.072
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.945
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.670
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.042
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.065
After features/support/hooks.rb:339 0.741
After features/support/hooks.rb:108 0.000