Project Number Date
test_Tails_ISO_devel 4126 17 Dec 2025, 21:08

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 13:40.781 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:44.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 32.623
When I start Tails from USB drive "old" with network unplugged 1:6.523
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:331 3.854
After features/support/hooks.rb:100 0.027
Tags: @product
1:37.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:2.486
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 29.183
And I take note of which tps features are available 1.238
Then a Tails persistence partition exists on USB drive "old" 0.681
And I shutdown Tails and wait for the computer to power off 3.088
After features/support/hooks.rb:331 0.297
After features/support/hooks.rb:100 0.010
Tags: @product
1:43.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.560
Then Tails is running from USB drive "old" 0.297
And all tps features are active 1.939
When I write some files expected to persist 1.475
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.150
And I take note of which tps features are available 0.423
And I shutdown Tails and wait for the computer to power off 7.465
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.661
After features/support/hooks.rb:331 0.214
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.600
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.603
And I log in to a new session 16.769
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.534
And I plug USB drive "to_upgrade" 2.817
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.739
Then the running Tails is installed on USB drive "to_upgrade" 20.735
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 4.002
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.112
Then all tps features from the old Tails version are active 1.454
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 2.966
And the expected persistent files created with the old Tails version are present in the filesystem 1.231
And all persistent directories from the old Tails version have safe access rights 2.061
After features/support/hooks.rb:331 1.016
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
4:16.971
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.561
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.069
And Tor is ready 14.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.567
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.952
Given I shutdown Tails and wait for the computer to power off 11.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.893
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.186
# 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.244
When the network is plugged 0.067
And Tor is ready 12.201
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.635
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.491
Given I shutdown Tails and wait for the computer to power off 4.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.450
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.319
And the file system changes introduced in version 6.3~testoverlayfs are present 0.423
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.060
And Tor is ready 13.351
Then the Upgrader considers the system as up-to-date 0.108
# 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 6.794
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.487
After features/support/hooks.rb:331 1.095
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.475
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.455
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 10.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.613
After features/support/hooks.rb:331 1.137
After features/support/hooks.rb:100 0.000