Project Number Date
test_Tails_ISO_stable 6616 31 Aug 2026, 11:35

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:21.095 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
56.121
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.135
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.100
And I write an old version of the Tails USB image to disk "old" 13.759
When I start Tails from USB drive "old" with network unplugged 38.502
Then the boot device has safe access rights 1.958
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 1.643
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.756
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 49.672
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 23.541
And I take note of which tps features are available 6.795
Then a Tails persistence partition exists on USB drive "old" 0.457
And I shutdown Tails and wait for the computer to power off 3.923
After features/support/hooks.rb:339 0.636
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.801
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.003
Then Tails is running from USB drive "old" 0.261
And all tps features are active 7.318
When I write some files expected to persist 1.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.102
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 1.818
And I take note of which tps features are available 6.762
And I shutdown Tails and wait for the computer to power off 4.070
# 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.813
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.189
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.730
And I log in to a new session 13.420
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.674
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.645
Then the running Tails is installed on USB drive "to_upgrade" 18.227
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.648
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.066
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.641
Then all tps features from the old Tails version are active 1.270
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.256
And the expected persistent files created with the old Tails version are present in the filesystem 1.000
And all persistent directories from the old Tails version have safe access rights 1.595
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.070
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.152
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.037
And Tor is ready 13.338
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.996
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.563
Given I shutdown Tails and wait for the computer to power off 5.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.705
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.164
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.148
When the network is plugged 0.027
And Tor is ready 11.171
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.948
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.764
Given I shutdown Tails and wait for the computer to power off 4.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.631
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 8.607
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.027
And Tor is ready 11.416
Then the Upgrader considers the system as up-to-date 0.109
# 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.640
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
20.089
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.333
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 9.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.106
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.000