Project Number Date
test_Tails_ISO_stable 6052 12 Jan 2026, 11:24

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:37.333 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:14.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.607
When I start Tails from USB drive "old" with network unplugged 56.753
Then the boot device has safe access rights 2.623
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 3.881
After features/support/hooks.rb:100 0.046
Tags: @product
1:24.977
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.674
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 23.849
And I take note of which tps features are available 0.664
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 7.959
After features/support/hooks.rb:331 0.377
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.431
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.587
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.112
When I write some files expected to persist 1.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 1.765
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 7.886
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.760
After features/support/hooks.rb:331 0.394
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.883
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 without a persistent partition and stopped at Tails Greeter's login screen 8.369
And I log in to a new session 13.033
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.804
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.786
Then the running Tails is installed on USB drive "to_upgrade" 15.352
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 3.747
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.622
Then all tps features from the old Tails version are active 0.942
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.560
And the expected persistent files created with the old Tails version are present in the filesystem 1.114
And all persistent directories from the old Tails version have safe access rights 1.837
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
3:29.039
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.119
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.018
And Tor is ready 11.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.344
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.478
Given I shutdown Tails and wait for the computer to power off 9.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.569
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.213
When the network is plugged 0.020
And Tor is ready 10.063
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.979
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.317
Given I shutdown Tails and wait for the computer to power off 7.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.650
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.019
And Tor is ready 11.023
Then the Upgrader considers the system as up-to-date 10.518
# 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.755
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
46.890
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.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 38.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
After features/support/hooks.rb:331 0.806
After features/support/hooks.rb:100 0.000