Project Number Date
test_Tails_ISO_stable 5999 10 Dec 2025, 20:28

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:49.851 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:55.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 27.387
When I start Tails from USB drive "old" with network unplugged 1:23.280
Then the boot device has safe access rights 3.076
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 3.829
After features/support/hooks.rb:100 0.007
Tags: @product
2:1.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:22.152
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 29.111
And I take note of which tps features are available 1.134
Then a Tails persistence partition exists on USB drive "old" 0.685
And I shutdown Tails and wait for the computer to power off 7.618
After features/support/hooks.rb:331 0.378
After features/support/hooks.rb:100 0.006
Tags: @product
2:7.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.472
Then Tails is running from USB drive "old" 0.428
And all tps features are active 1.857
When I write some files expected to persist 1.618
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.354
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 7.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.870
After features/support/hooks.rb:331 0.264
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.589
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 without a persistent partition and stopped at Tails Greeter's login screen 9.963
And I log in to a new session 10.303
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.530
And I plug USB drive "to_upgrade" 2.649
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.789
Then the running Tails is installed on USB drive "to_upgrade" 18.969
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 3.742
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.364
Then all tps features from the old Tails version are active 1.501
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.305
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.325
After features/support/hooks.rb:331 1.038
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:43.695
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 10.502
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.377
When the network is plugged 0.064
And Tor is ready 13.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.064
Given I shutdown Tails and wait for the computer to power off 7.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.168
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.965
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.226
# 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.302
When the network is plugged 0.071
And Tor is ready 14.818
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.950
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.280
Given I shutdown Tails and wait for the computer to power off 7.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.600
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.579
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.190
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.094
And Tor is ready 40.961
Then the Upgrader considers the system as up-to-date 0.178
# 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.158
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.720
After features/support/hooks.rb:331 0.998
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
22.919
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 10.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 2.161
And Tor is ready 9.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.592
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.000