Project Number Date
test_Tails_ISO_stable 5927 03 Nov 2025, 13:25

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 16:21.422 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:43.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.277
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.075
And I write an old version of the Tails USB image to disk "old" 26.475
When I start Tails from USB drive "old" with network unplugged 1:11.562
Then the boot device has safe access rights 3.396
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.550
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:28.454
Then Tails is running from USB drive "old" 0.541
And I create a persistent partition 29.622
And I take note of which tps features are available 1.233
Then a Tails persistence partition exists on USB drive "old" 0.696
And I shutdown Tails and wait for the computer to power off 8.462
After features/support/hooks.rb:331 0.223
After features/support/hooks.rb:100 0.016
Tags: @product
2:17.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.356
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.876
Then Tails is running from USB drive "old" 0.767
And all tps features are active 2.316
When I write some files expected to persist 1.800
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.589
And I take note of which tps features are available 0.596
And I shutdown Tails and wait for the computer to power off 7.651
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.495
After features/support/hooks.rb:331 0.470
After features/support/hooks.rb:100 0.012
Tags: @product
2:29.982
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 11.329
And I log in to a new session 17.185
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.204
And I plug USB drive "to_upgrade" 2.328
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.356
Then the running Tails is installed on USB drive "to_upgrade" 22.060
And I unplug USB drive "to_upgrade" 0.306
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:331 4.234
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.235
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.494
Then all tps features from the old Tails version are active 2.056
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.571
And all persistent directories from the old Tails version have safe access rights 2.516
After features/support/hooks.rb:331 0.800
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:20.756
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.135
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.079
And Tor is ready 14.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.930
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.901
Given I shutdown Tails and wait for the computer to power off 11.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.129
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.235
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.273
When the network is plugged 0.087
And Tor is ready 12.350
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.543
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.776
Given I shutdown Tails and wait for the computer to power off 8.018
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.167
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.683
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.071
And Tor is ready 11.574
Then the Upgrader considers the system as up-to-date 10.794
# 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.759
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.456
After features/support/hooks.rb:331 0.958
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.895
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 with a persistent partition enabled and logged in 10.226
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.140
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 12.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.997
After features/support/hooks.rb:331 1.088
After features/support/hooks.rb:100 0.000