Project Number Date
test_Tails_ISO_stable 6613 28 Aug 2026, 11:34

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:12.213 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:0.189
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.369
When I start Tails from USB drive "old" with network unplugged 42.920
Then the boot device has safe access rights 2.164
And Tails is running from USB drive "old" 0.207
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.141
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.169
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.525
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 47.043
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 23.501
And I take note of which tps features are available 6.552
Then a Tails persistence partition exists on USB drive "old" 0.557
And I shutdown Tails and wait for the computer to power off 2.581
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.308
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.551
Then Tails is running from USB drive "old" 0.255
And all tps features are active 7.109
When I write some files expected to persist 1.011
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.213
And all persistent directories from the old Tails version have safe access rights 1.870
And I take note of which tps features are available 6.025
And I shutdown Tails and wait for the computer to power off 2.550
# 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.451
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.217
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.263
And I log in to a new session 12.229
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.606
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.065
Then the running Tails is installed on USB drive "to_upgrade" 17.553
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.690
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.565
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.610
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.145
And the boot device has safe access rights 2.697
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.946
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.156
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.514
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.030
And Tor is ready 12.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.529
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.784
Given I shutdown Tails and wait for the computer to power off 5.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.934
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.173
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.162
When the network is plugged 0.037
And Tor is ready 10.227
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.933
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.924
Given I shutdown Tails and wait for the computer to power off 2.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.405
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.884
And the file system changes introduced in version 6.3~testoverlayfs are present 0.308
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.155
When the network is plugged 0.048
And Tor is ready 10.184
Then the Upgrader considers the system as up-to-date 10.466
# 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.638
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.249
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.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.216
After features/support/hooks.rb:339 0.865
After features/support/hooks.rb:108 0.000