Project Number Date
test_Tails_ISO_devel 4232 15 Feb 2026, 11:55

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 11:51.907 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:9.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.039
When I start Tails from USB drive "old" with network unplugged 50.839
Then the boot device has safe access rights 3.056
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.126
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.233
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 57.729
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 24.776
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 2.784
After features/support/hooks.rb:331 0.487
After features/support/hooks.rb:100 0.005
Tags: @product
1:28.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.129
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.114
When I write some files expected to persist 1.446
# 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.361
And all persistent directories from the old Tails version have safe access rights 2.188
And I take note of which tps features are available 0.172
And I shutdown Tails and wait for the computer to power off 6.813
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.999
After features/support/hooks.rb:331 0.540
After features/support/hooks.rb:100 0.006
Tags: @product
2:16.902
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.260
And I log in to a new session 12.680
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.010
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.999
Then the running Tails is installed on USB drive "to_upgrade" 17.231
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.274
After features/support/hooks.rb:331 3.949
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.308
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.609
Then all tps features from the old Tails version are active 0.916
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.825
And the expected persistent files created with the old Tails version are present in the filesystem 1.186
And all persistent directories from the old Tails version have safe access rights 2.468
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
3:56.105
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 8.632
And no SquashFS delta is installed 0.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.016
And Tor is ready 15.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.644
Given I shutdown Tails and wait for the computer to power off 20.179
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.522
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.580
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.265
When the network is plugged 0.016
And Tor is ready 11.555
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.684
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.877
Given I shutdown Tails and wait for the computer to power off 4.181
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.474
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.015
And Tor is ready 11.597
Then the Upgrader considers the system as up-to-date 10.523
# 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.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:331 0.925
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
22.090
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.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.587
After features/support/hooks.rb:331 0.662
After features/support/hooks.rb:100 0.000