Project Number Date
test_Tails_ISO_devel 4273 12 Mar 2026, 11:08

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 12:59.775 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:13.934
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.457
When I start Tails from USB drive "old" with network unplugged 56.333
Then the boot device has safe access rights 2.346
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:331 3.890
After features/support/hooks.rb:100 0.017
Tags: @product
1:24.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 53.811
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 25.103
And I take note of which tps features are available 0.777
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 4.413
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.017
Tags: @product
1:28.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.281
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.013
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 1.844
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 8.219
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.205
After features/support/hooks.rb:331 0.490
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.860
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 without a persistent partition and stopped at Tails Greeter's login screen 8.264
And I log in to a new session 10.744
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.765
And I plug USB drive "to_upgrade" 2.284
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.161
Then the running Tails is installed on USB drive "to_upgrade" 16.341
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 1.917
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.216
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.252
Then all tps features from the old Tails version are active 1.080
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.463
And the expected persistent files created with the old Tails version are present in the filesystem 1.846
And all persistent directories from the old Tails version have safe access rights 2.255
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
4:39.624
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.447
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.013
And Tor is ready 20.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.817
Given I shutdown Tails and wait for the computer to power off 20.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.322
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# 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.213
When the network is plugged 0.019
And Tor is ready 20.902
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.430
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.710
Given I shutdown Tails and wait for the computer to power off 17.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.295
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.416
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.016
And Tor is ready 21.451
Then the Upgrader considers the system as up-to-date 0.104
# 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 4.927
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.383
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
49.250
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.517
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
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.039
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 41.060
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
After features/support/hooks.rb:331 0.963
After features/support/hooks.rb:100 0.000