Project Number Date
test_Tails_ISO_devel 4347 15 Apr 2026, 13:29

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:8.245 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:9.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 15.017
When I start Tails from USB drive "old" with network unplugged 48.801
Then the boot device has safe access rights 3.423
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.267
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 3.475
After features/support/hooks.rb:100 0.009
Tags: @product
1:32.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login 59.653
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.383
And I take note of which tps features are available 0.701
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 7.005
After features/support/hooks.rb:331 0.227
After features/support/hooks.rb:100 0.008
Tags: @product
1:38.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.549
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.155
When I write some files expected to persist 1.249
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.391
And I take note of which tps features are available 0.189
And I shutdown Tails and wait for the computer to power off 7.242
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.929
After features/support/hooks.rb:331 0.293
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.039
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 8.764
And I log in to a new session 18.194
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.061
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.274
Then the running Tails is installed on USB drive "to_upgrade" 18.119
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:331 3.849
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.849
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.291
And the expected persistent files created with the old Tails version are present in the filesystem 1.954
And all persistent directories from the old Tails version have safe access rights 2.263
After features/support/hooks.rb:331 0.947
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:33.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.196
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.019
And Tor is ready 27.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.694
Given I shutdown Tails and wait for the computer to power off 22.191
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.648
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.986
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
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.142
# 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.230
When the network is plugged 0.017
And Tor is ready 22.424
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.484
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.010
Given I shutdown Tails and wait for the computer to power off 18.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.659
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.326
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.027
And Tor is ready 22.323
Then the Upgrader considers the system as up-to-date 0.123
# 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.194
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:331 0.827
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
32.386
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 9.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 22.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.417
After features/support/hooks.rb:331 0.901
After features/support/hooks.rb:100 0.000