Project Number Date
test_Tails_ISO_stable 6054 13 Jan 2026, 08:34

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 14:4.358 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:37.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.132
And I write an old version of the Tails USB image to disk "old" 27.611
When I start Tails from USB drive "old" with network unplugged 1:3.570
Then the boot device has safe access rights 3.699
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:331 3.920
After features/support/hooks.rb:100 0.012
Tags: @product
1:38.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:3.350
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 29.052
And I take note of which tps features are available 1.170
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 3.494
After features/support/hooks.rb:331 0.529
After features/support/hooks.rb:100 0.010
Tags: @product
1:54.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:19.626
Then Tails is running from USB drive "old" 0.732
And all tps features are active 2.124
When I write some files expected to persist 1.678
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.694
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 7.765
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.255
After features/support/hooks.rb:331 0.310
After features/support/hooks.rb:100 0.022
Tags: @product
2:25.693
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 without a persistent partition and stopped at Tails Greeter's login screen 10.217
And I log in to a new session 10.126
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.816
And I plug USB drive "to_upgrade" 3.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.590
Then the running Tails is installed on USB drive "to_upgrade" 19.340
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 3.809
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.586
Then all tps features from the old Tails version are active 1.877
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.307
And the expected persistent files created with the old Tails version are present in the filesystem 1.390
And all persistent directories from the old Tails version have safe access rights 2.749
After features/support/hooks.rb:331 1.036
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:43.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.590
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.085
And Tor is ready 12.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.836
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.567
Given I shutdown Tails and wait for the computer to power off 7.825
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.812
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.125
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.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.250
When the network is plugged 0.064
And Tor is ready 42.491
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.649
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.972
Given I shutdown Tails and wait for the computer to power off 7.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.729
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.239
And the file system changes introduced in version 6.3~testoverlayfs are present 0.423
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.058
And Tor is ready 11.491
Then the Upgrader considers the system as up-to-date 10.619
# 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.288
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.506
After features/support/hooks.rb:331 1.223
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
22.187
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 9.998
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.055
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 10.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.752
After features/support/hooks.rb:331 0.717
After features/support/hooks.rb:100 0.000