Project Number Date
test_Tails_ISO_devel 4146 02 Jan 2026, 07:51

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:54.161 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.985
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.379
When I start Tails from USB drive "old" with network unplugged 43.626
Then the boot device has safe access rights 2.250
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.588
After features/support/hooks.rb:100 0.035
Tags: @product
1:24.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 51.231
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.581
And I take note of which tps features are available 0.636
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 8.166
After features/support/hooks.rb:331 0.429
After features/support/hooks.rb:100 0.007
Tags: @product
1:22.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.516
Then Tails is running from USB drive "old" 0.196
And all tps features are active 1.191
When I write some files expected to persist 1.260
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.755
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 8.074
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.578
After features/support/hooks.rb:331 0.564
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.073
And I log in to a new session 12.211
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.777
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.554
Then the running Tails is installed on USB drive "to_upgrade" 14.425
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 3.801
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.092
Then all tps features from the old Tails version are active 0.914
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.592
And the expected persistent files created with the old Tails version are present in the filesystem 1.071
And all persistent directories from the old Tails version have safe access rights 1.931
After features/support/hooks.rb:331 0.779
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:32.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.058
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.017
And Tor is ready 12.835
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.653
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.311
Given I shutdown Tails and wait for the computer to power off 9.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.570
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
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.134
# 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.245
When the network is plugged 0.019
And Tor is ready 10.552
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.642
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.219
Given I shutdown Tails and wait for the computer to power off 7.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.916
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.018
And Tor is ready 11.346
Then the Upgrader considers the system as up-to-date 10.490
# 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.804
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:331 0.810
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.366
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.489
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.012
And Tor is ready 9.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.407
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.000