Project Number Date
test_Tails_ISO_stable 6004 12 Dec 2025, 12:40

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 13:44.509 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:23.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 27.027
When I start Tails from USB drive "old" with network unplugged 51.128
Then the boot device has safe access rights 3.643
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:331 3.863
After features/support/hooks.rb:100 0.012
Tags: @product
1:42.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:5.336
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 29.900
And I take note of which tps features are available 1.226
Then a Tails persistence partition exists on USB drive "old" 0.705
And I shutdown Tails and wait for the computer to power off 4.628
After features/support/hooks.rb:331 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
1:51.163
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.418
Then Tails is running from USB drive "old" 0.283
And all tps features are active 1.741
When I write some files expected to persist 1.589
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.232
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 8.841
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.762
After features/support/hooks.rb:331 0.285
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.794
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 10.130
And I log in to a new session 11.802
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.763
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.171
Then the running Tails is installed on USB drive "to_upgrade" 21.172
And I unplug USB drive "to_upgrade" 0.259
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 3.770
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.922
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.186
Then all tps features from the old Tails version are active 1.533
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.066
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.087
After features/support/hooks.rb:331 0.925
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:24.068
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.018
And no SquashFS delta is installed 0.061
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.049
And Tor is ready 12.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.710
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.255
Given I shutdown Tails and wait for the computer to power off 7.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.976
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 5.962
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.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.231
# 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.234
When the network is plugged 2.450
And Tor is ready 11.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.710
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.411
Given I shutdown Tails and wait for the computer to power off 8.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.165
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.456
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.114
And Tor is ready 12.997
Then the Upgrader considers the system as up-to-date 0.123
# 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 8.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.623
After features/support/hooks.rb:331 1.305
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
21.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.814
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 10.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.983
After features/support/hooks.rb:331 1.042
After features/support/hooks.rb:100 0.000