Project Number Date
test_Tails_ISO_stable 5965 23 Nov 2025, 12:30

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 16:12.892 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:55.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 32.425
When I start Tails from USB drive "old" with network unplugged 1:17.850
Then the boot device has safe access rights 3.416
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:331 3.832
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:24.022
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 29.089
And I take note of which tps features are available 1.220
Then a Tails persistence partition exists on USB drive "old" 0.696
And I shutdown Tails and wait for the computer to power off 7.691
After features/support/hooks.rb:331 0.256
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.963
Then Tails is running from USB drive "old" 0.608
And all tps features are active 1.732
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.176
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.681
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.180
After features/support/hooks.rb:331 0.502
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.413
And I log in to a new session 17.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.764
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.607
Then the running Tails is installed on USB drive "to_upgrade" 20.803
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:331 3.951
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.066
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.840
Then all tps features from the old Tails version are active 1.352
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.905
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 2.227
After features/support/hooks.rb:331 1.101
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:26.831
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.384
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.055
And Tor is ready 15.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.688
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.738
Given I shutdown Tails and wait for the computer to power off 10.985
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.252
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.965
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.247
When the network is plugged 0.054
And Tor is ready 12.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.832
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 1:34.416
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.046
And the file system changes introduced in version 6.3~testoverlayfs are present 0.577
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.092
And Tor is ready 41.800
Then the Upgrader considers the system as up-to-date 0.204
# 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 5.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.485
After features/support/hooks.rb:331 0.910
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 10.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.669
After features/support/hooks.rb:331 0.856
After features/support/hooks.rb:100 0.000