Project Number Date
test_Tails_ISO_devel 4662 07 Oct 2026, 11:36

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 10:50.017 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:6.894
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.031
When I start Tails from USB drive "old" with network unplugged 50.328
Then the boot device has safe access rights 1.810
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.041
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.633
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.187
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 46.645
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 23.186
And I take note of which tps features are available 6.018
Then a Tails persistence partition exists on USB drive "old" 0.486
And I shutdown Tails and wait for the computer to power off 2.553
After features/support/hooks.rb:339 0.203
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.287
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.142
Then Tails is running from USB drive "old" 0.201
And all tps features are active 6.446
When I write some files expected to persist 0.923
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.236
And all persistent directories from the old Tails version have safe access rights 1.614
And I take note of which tps features are available 5.911
And I shutdown Tails and wait for the computer to power off 2.507
# 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.024
After features/support/hooks.rb:339 0.516
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.454
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.520
And I log in to a new session 10.998
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.647
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.757
Then the running Tails is installed on USB drive "to_upgrade" 16.922
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.569
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.020
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 59.574
Then all tps features from the old Tails version are active 0.978
And Tails is running from USB drive "to_upgrade" 0.197
And the boot device has safe access rights 1.834
And the expected persistent files created with the old Tails version are present in the filesystem 0.913
And all persistent directories from the old Tails version have safe access rights 1.443
After features/support/hooks.rb:339 0.632
After features/support/hooks.rb:108 0.005
3:22.952
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.077
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.257
When the network is plugged 0.023
And Tor is ready 13.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.833
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.380
Given I shutdown Tails and wait for the computer to power off 5.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.566
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.035
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.177
When the network is plugged 0.034
And Tor is ready 10.256
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.286
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.391
Given I shutdown Tails and wait for the computer to power off 3.932
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.032
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.528
And the file system changes introduced in version 6.3~testoverlayfs are present 0.287
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.031
And Tor is ready 10.069
Then the Upgrader considers the system as up-to-date 0.082
# 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.534
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:339 0.877
After features/support/hooks.rb:108 0.011
18.220
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.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 8.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.484
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.000