Project Number Date
test_Tails_ISO_stable 5943 11 Nov 2025, 15:50

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 20:1.813 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:23.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 42.007
When I start Tails from USB drive "old" with network unplugged 1:36.124
Then the boot device has safe access rights 3.399
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:331 4.028
After features/support/hooks.rb:100 0.042
Tags: @product
2:11.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:30.723
Then Tails is running from USB drive "old" 0.840
And I create a persistent partition 29.555
And I take note of which tps features are available 1.116
Then a Tails persistence partition exists on USB drive "old" 0.661
And I shutdown Tails and wait for the computer to power off 8.615
After features/support/hooks.rb:331 0.422
After features/support/hooks.rb:100 0.029
Tags: @product
2:10.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.104
Then Tails is running from USB drive "old" 0.776
And all tps features are active 2.282
When I write some files expected to persist 1.640
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.552
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 3.093
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.565
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.940
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 without a persistent partition and stopped at Tails Greeter's login screen 12.565
And I log in to a new session 22.114
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.260
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.275
Then the running Tails is installed on USB drive "to_upgrade" 27.790
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:331 4.095
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.508
Then all tps features from the old Tails version are active 24.496
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 6.064
And the expected persistent files created with the old Tails version are present in the filesystem 5.314
And all persistent directories from the old Tails version have safe access rights 3.559
After features/support/hooks.rb:331 9.890
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:15.199
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 with a persistent partition enabled and logged in 58.072
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 9.196
And Tor is ready 19.458
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.814
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 37.640
Given I shutdown Tails and wait for the computer to power off 13.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.256
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.280
And the file system changes introduced in version 6.2~testoverlayfs are present 0.403
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.311
When the network is plugged 0.054
And Tor is ready 18.937
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.657
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.708
Given I shutdown Tails and wait for the computer to power off 8.220
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.555
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.539
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.051
And Tor is ready 10.856
Then the Upgrader considers the system as up-to-date 0.270
# 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.766
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.607
After features/support/hooks.rb:331 1.138
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
27.291
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 11.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 14.074
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.609
After features/support/hooks.rb:331 1.120
After features/support/hooks.rb:100 0.000