Project Number Date
test_Tails_ISO_devel 4187 24 Jan 2026, 08:27

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:59.753 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:1.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.016
When I start Tails from USB drive "old" with network unplugged 42.797
Then the boot device has safe access rights 2.702
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 3.655
After features/support/hooks.rb:100 0.005
Tags: @product
1:27.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.763
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 23.966
And I take note of which tps features are available 0.630
Then a Tails persistence partition exists on USB drive "old" 0.489
And I shutdown Tails and wait for the computer to power off 8.175
After features/support/hooks.rb:331 0.590
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.891
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.127
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.136
When I write some files expected to persist 1.441
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.230
And I take note of which tps features are available 0.214
And I shutdown Tails and wait for the computer to power off 4.187
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.503
After features/support/hooks.rb:331 0.483
After features/support/hooks.rb:100 0.006
Tags: @product
2:15.502
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 without a persistent partition and stopped at Tails Greeter's login screen 8.275
And I log in to a new session 12.018
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.795
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.484
Then the running Tails is installed on USB drive "to_upgrade" 16.344
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:331 3.716
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.257
Then all tps features from the old Tails version are active 0.940
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.427
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.945
After features/support/hooks.rb:331 0.774
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:49.780
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 9.019
And no SquashFS delta is installed 0.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.060
And Tor is ready 13.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.939
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.230
Given I shutdown Tails and wait for the computer to power off 21.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.289
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.513
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.240
When the network is plugged 0.028
And Tor is ready 11.353
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.166
Given I shutdown Tails and wait for the computer to power off 8.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.253
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.233
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.014
And Tor is ready 10.657
Then the Upgrader considers the system as up-to-date 0.142
# 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.260
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.559
After features/support/hooks.rb:331 1.160
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
48.922
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 with a persistent partition enabled and logged in 7.841
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 40.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.392
After features/support/hooks.rb:331 0.901
After features/support/hooks.rb:100 0.000