Project Number Date
test_Tails_ISO_stable 6041 07 Jan 2026, 07:37

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:12.007 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:15.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.029
When I start Tails from USB drive "old" with network unplugged 58.310
Then the boot device has safe access rights 2.391
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.621
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.920
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 "old" with network unplugged and I login 52.446
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.738
And I take note of which tps features are available 0.639
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 8.270
After features/support/hooks.rb:331 0.479
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.771
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 59.550
Then Tails is running from USB drive "old" 0.240
And all tps features are active 1.141
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.336
And all persistent directories from the old Tails version have safe access rights 1.785
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 7.860
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.188
After features/support/hooks.rb:331 0.544
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.186
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.083
And I log in to a new session 11.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.258
Then the running Tails is installed on USB drive "to_upgrade" 15.867
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 7.241
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.587
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.242
And the expected persistent files created with the old Tails version are present in the filesystem 0.973
And all persistent directories from the old Tails version have safe access rights 1.774
After features/support/hooks.rb:331 0.903
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
3:31.798
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.205
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.015
And Tor is ready 12.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.299
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.814
Given I shutdown Tails and wait for the computer to power off 9.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.905
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.044
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.179
When the network is plugged 0.017
And Tor is ready 9.650
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 3.946
Given I shutdown Tails and wait for the computer to power off 7.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.157
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.040
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.013
And Tor is ready 9.708
Then the Upgrader considers the system as up-to-date 10.517
# 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.173
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:331 0.599
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
17.963
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.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.055
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.362
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.026
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.000