Project Number Date
test_Tails_ISO_devel 4124 17 Dec 2025, 09:12

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 15:15.390 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:31.016
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.095
And I write an old version of the Tails USB image to disk "old" 27.763
When I start Tails from USB drive "old" with network unplugged 57.691
Then the boot device has safe access rights 3.315
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:331 3.901
After features/support/hooks.rb:100 0.020
Tags: @product
1:58.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:8.043
Then Tails is running from USB drive "old" 0.631
And I create a persistent partition 39.706
And I take note of which tps features are available 1.147
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 8.232
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.012
Tags: @product
2:7.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.027
Then Tails is running from USB drive "old" 0.788
And all tps features are active 1.985
When I write some files expected to persist 1.980
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.535
And all persistent directories from the old Tails version have safe access rights 2.627
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 10.539
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.939
After features/support/hooks.rb:331 0.138
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.759
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.413
And I log in to a new session 12.585
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.405
And I plug USB drive "to_upgrade" 9.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.608
Then the running Tails is installed on USB drive "to_upgrade" 21.983
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:331 3.639
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:22.121
Then all tps features from the old Tails version are active 1.819
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 3.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.579
And all persistent directories from the old Tails version have safe access rights 3.535
After features/support/hooks.rb:331 1.660
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
5:6.467
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 with a persistent partition enabled and logged in 14.741
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.506
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.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.051
And Tor is ready 12.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.887
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.015
Given I shutdown Tails and wait for the computer to power off 7.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.095
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 3.131
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.252
# 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.420
When the network is plugged 0.090
And Tor is ready 42.519
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.653
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.910
Given I shutdown Tails and wait for the computer to power off 9.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.486
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.684
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.048
And Tor is ready 13.785
Then the Upgrader considers the system as up-to-date 0.160
# 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 7.132
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.638
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
21.459
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.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
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.108
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 10.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.579
After features/support/hooks.rb:331 0.955
After features/support/hooks.rb:100 0.000