Project Number Date
test_Tails_ISO_stable 6021 24 Dec 2025, 11:48

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:12.292 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:42.075
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 31.379
When I start Tails from USB drive "old" with network unplugged 1:5.791
Then the boot device has safe access rights 2.894
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.909
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 59.677
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 26.802
And I take note of which tps features are available 1.077
Then a Tails persistence partition exists on USB drive "old" 0.671
And I shutdown Tails and wait for the computer to power off 3.092
After features/support/hooks.rb:331 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
1:39.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.912
Then Tails is running from USB drive "old" 0.302
And all tps features are active 1.681
When I write some files expected to persist 1.480
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.214
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 7.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.475
After features/support/hooks.rb:331 0.239
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.094
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.596
And I log in to a new session 16.605
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.979
And I plug USB drive "to_upgrade" 2.706
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.432
Then the running Tails is installed on USB drive "to_upgrade" 19.403
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:331 3.701
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.127
Then all tps features from the old Tails version are active 1.352
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 2.698
And the expected persistent files created with the old Tails version are present in the filesystem 1.268
And all persistent directories from the old Tails version have safe access rights 2.170
After features/support/hooks.rb:331 0.825
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
3:56.863
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 with a persistent partition enabled and logged in 11.126
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.446
When the network is plugged 0.053
And Tor is ready 14.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.565
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.554
Given I shutdown Tails and wait for the computer to power off 10.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.247
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.958
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
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.162
# 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.210
When the network is plugged 0.053
And Tor is ready 10.803
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.863
Given I shutdown Tails and wait for the computer to power off 7.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.198
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.906
And the file system changes introduced in version 6.3~testoverlayfs are present 0.405
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.064
And Tor is ready 12.507
Then the Upgrader considers the system as up-to-date 0.125
# 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 5.354
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.539
After features/support/hooks.rb:331 1.168
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.713
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 with a persistent partition enabled and logged in 10.386
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 11.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.585
After features/support/hooks.rb:331 1.150
After features/support/hooks.rb:100 0.000