Project Number Date
test_Tails_ISO_stable 5958 17 Nov 2025, 12:42

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:13.232 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
2:8.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 33.200
When I start Tails from USB drive "old" with network unplugged 1:30.501
Then the boot device has safe access rights 2.895
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:331 4.096
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.756
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:27.084
Then Tails is running from USB drive "old" 0.591
And I create a persistent partition 28.766
And I take note of which tps features are available 1.546
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 7.780
After features/support/hooks.rb:331 0.301
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.832
Then Tails is running from USB drive "old" 0.740
And all tps features are active 2.120
When I write some files expected to persist 1.626
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 2.093
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 8.075
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.983
After features/support/hooks.rb:331 0.232
After features/support/hooks.rb:100 0.013
Tags: @product
2:37.393
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 12.918
And I log in to a new session 18.738
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.597
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.344
Then the running Tails is installed on USB drive "to_upgrade" 21.051
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 4.286
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.820
Then all tps features from the old Tails version are active 1.457
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.191
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.295
After features/support/hooks.rb:331 0.712
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:56.108
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 13.441
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.082
And Tor is ready 14.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.972
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.615
Given I shutdown Tails and wait for the computer to power off 10.987
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.206
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.024
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.244
When the network is plugged 0.057
And Tor is ready 11.859
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.697
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.738
Given I shutdown Tails and wait for the computer to power off 4.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.292
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.478
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.064
And Tor is ready 11.263
Then the Upgrader considers the system as up-to-date 0.438
# 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.188
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.435
After features/support/hooks.rb:331 1.148
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.679
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 10.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 11.809
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.546
After features/support/hooks.rb:331 0.614
After features/support/hooks.rb:100 0.000