Project Number Date
test_Tails_ISO_devel 4338 13 Apr 2026, 17: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 11:51.638 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
56.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.089
When I start Tails from USB drive "old" with network unplugged 39.354
Then the boot device has safe access rights 2.497
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.445
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.372
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.251
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 23.644
And I take note of which tps features are available 0.686
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 7.923
After features/support/hooks.rb:331 0.479
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.824
Then Tails is running from USB drive "old" 0.230
And all tps features are active 1.105
When I write some files expected to persist 1.169
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.519
And all persistent directories from the old Tails version have safe access rights 1.848
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 8.074
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.731
After features/support/hooks.rb:331 0.383
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.132
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 without a persistent partition and stopped at Tails Greeter's login screen 7.722
And I log in to a new session 12.036
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.755
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.854
Then the running Tails is installed on USB drive "to_upgrade" 15.224
And I unplug USB drive "to_upgrade" 0.175
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:331 0.677
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.574
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.031
And all persistent directories from the old Tails version have safe access rights 1.787
After features/support/hooks.rb:331 0.614
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
4:24.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.115
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.018
And Tor is ready 19.453
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.642
Given I shutdown Tails and wait for the computer to power off 19.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.893
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.178
When the network is plugged 0.022
And Tor is ready 21.596
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.832
Given I shutdown Tails and wait for the computer to power off 13.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.168
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.016
And Tor is ready 20.743
Then the Upgrader considers the system as up-to-date 0.099
# 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 4.202
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:331 0.775
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
26.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.598
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.889
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.343
After features/support/hooks.rb:331 0.635
After features/support/hooks.rb:100 0.000