Project Number Date
test_Tails_ISO_devel 4230 13 Feb 2026, 11:49

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 12:1.499 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:8.717
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.210
When I start Tails from USB drive "old" with network unplugged 49.589
Then the boot device has safe access rights 3.094
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.432
After features/support/hooks.rb:100 0.047
Tags: @product
1:32.918
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 57.102
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 26.133
And I take note of which tps features are available 1.036
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 7.538
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.028
Tags: @product
1:34.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.151
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.169
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.331
When I write some files expected to persist 1.520
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 2.793
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.146
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.088
After features/support/hooks.rb:331 0.253
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.253
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 without a persistent partition and stopped at Tails Greeter's login screen 8.464
And I log in to a new session 11.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.981
And I plug USB drive "to_upgrade" 2.296
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.704
Then the running Tails is installed on USB drive "to_upgrade" 16.764
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 0.804
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.484
Then all tps features from the old Tails version are active 1.389
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.051
And all persistent directories from the old Tails version have safe access rights 1.911
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:56.318
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.772
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.020
And Tor is ready 12.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.816
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.446
Given I shutdown Tails and wait for the computer to power off 11.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.037
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.176
When the network is plugged 0.018
And Tor is ready 11.135
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.981
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.353
Given I shutdown Tails and wait for the computer to power off 4.137
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.768
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.410
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.196
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.015
And Tor is ready 11.521
Then the Upgrader considers the system as up-to-date 10.586
# 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 4.670
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 0.670
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
20.209
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 with a persistent partition enabled and logged in 7.300
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.695
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.879
After features/support/hooks.rb:331 1.014
After features/support/hooks.rb:100 0.000