Project Number Date
test_Tails_ISO_stable 5922 31 Oct 2025, 09:04

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 17:58.028 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:59.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.231
When I start Tails from USB drive "old" with network unplugged 1:22.578
Then the boot device has safe access rights 2.827
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:331 4.250
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:25.776
Then Tails is running from USB drive "old" 0.634
And I create a persistent partition 29.348
And I take note of which tps features are available 1.197
Then a Tails persistence partition exists on USB drive "old" 0.899
And I shutdown Tails and wait for the computer to power off 8.059
After features/support/hooks.rb:331 0.448
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.043
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.731
Then Tails is running from USB drive "old" 0.828
And all tps features are active 1.828
When I write some files expected to persist 1.474
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 2.384
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 8.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.452
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.522
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 without a persistent partition and stopped at Tails Greeter's login screen 13.218
And I log in to a new session 17.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.187
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.254
Then the running Tails is installed on USB drive "to_upgrade" 21.571
And I unplug USB drive "to_upgrade" 0.270
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:331 4.175
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.307
Then all tps features from the old Tails version are active 1.657
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.353
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.427
After features/support/hooks.rb:331 0.721
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
6:35.051
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 13.459
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.059
And Tor is ready 44.917
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.627
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.158
Given I shutdown Tails and wait for the computer to power off 8.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.903
Then Tails is running version 6.2~testoverlayfs 0.139
And all tps features are active 9.633
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.237
When the network is plugged 0.052
And Tor is ready 15.896
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.564
Given I shutdown Tails and wait for the computer to power off 11.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.328
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.501
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.201
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.063
And Tor is ready 14.277
Then the Upgrader considers the system as up-to-date 0.240
# 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 6.027
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.567
After features/support/hooks.rb:331 0.849
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.872
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 11.969
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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 4.517
And Tor is ready 19.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.613
After features/support/hooks.rb:331 1.064
After features/support/hooks.rb:100 0.000