Project Number Date
test_Tails_ISO_stable 6261 04 Apr 2026, 06:56

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 11:44.999 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
59.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.238
When I start Tails from USB drive "old" with network unplugged 41.896
Then the boot device has safe access rights 2.585
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:331 3.681
After features/support/hooks.rb:100 0.023
Tags: @product
1:25.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 52.026
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 24.357
And I take note of which tps features are available 0.704
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 7.934
After features/support/hooks.rb:331 0.547
After features/support/hooks.rb:100 0.007
Tags: @product
1:17.232
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.419
Then Tails is running from USB drive "old" 0.293
And all tps features are active 1.173
When I write some files expected to persist 1.193
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
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.851
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 2.659
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.862
After features/support/hooks.rb:331 0.615
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.752
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.018
And I log in to a new session 11.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.915
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.237
Then the running Tails is installed on USB drive "to_upgrade" 15.349
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 1.889
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.948
Then all tps features from the old Tails version are active 0.919
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.616
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.943
After features/support/hooks.rb:331 1.047
After features/support/hooks.rb:100 0.006
4:20.679
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.096
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.014
And Tor is ready 19.645
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.144
Given I shutdown Tails and wait for the computer to power off 14.536
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.941
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 0.985
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.180
When the network is plugged 0.015
And Tor is ready 21.373
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.654
Given I shutdown Tails and wait for the computer to power off 17.034
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.722
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.016
And Tor is ready 21.281
Then the Upgrader considers the system as up-to-date 0.124
# 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.637
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:331 0.652
After features/support/hooks.rb:100 0.010
24.293
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.514
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.116
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.000