Project Number Date
test_Tails_ISO_21774-tor-0.4.9.12 1 09 Sep 2026, 17:55

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:42.858 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:17.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 15.879
When I start Tails from USB drive "old" with network unplugged 57.699
Then the boot device has safe access rights 2.286
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.356
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.700
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 50.565
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.484
And I take note of which tps features are available 6.175
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 2.603
After features/support/hooks.rb:339 0.132
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.389
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 with persistence enabled 1:0.143
Then Tails is running from USB drive "old" 0.187
And all tps features are active 7.394
When I write some files expected to persist 1.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.633
And I take note of which tps features are available 5.808
And I shutdown Tails and wait for the computer to power off 2.609
# 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.862
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.316
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.461
And I log in to a new session 12.208
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.651
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.177
Then the running Tails is installed on USB drive "to_upgrade" 18.275
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.940
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.887
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:4.509
Then all tps features from the old Tails version are active 1.061
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.163
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 1.793
After features/support/hooks.rb:339 0.891
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
3:45.637
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 8.507
And no SquashFS delta is installed 0.063
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.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.043
And Tor is ready 13.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.791
Given I shutdown Tails and wait for the computer to power off 5.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.779
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.510
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.106
# 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.027
And Tor is ready 10.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.986
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.080
Given I shutdown Tails and wait for the computer to power off 5.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.569
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.674
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.172
When the network is plugged 0.029
And Tor is ready 10.456
Then the Upgrader considers the system as up-to-date 10.413
# 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.793
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:339 0.767
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.308
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.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.179
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.041
And Tor is ready 9.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.038
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.000