Project Number Date
test_Tails_ISO_stable 6091 25 Jan 2026, 11:13

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:23.020 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:16.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.061
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.182
When I start Tails from USB drive "old" with network unplugged 59.221
Then the boot device has safe access rights 2.582
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 3.415
After features/support/hooks.rb:100 0.017
Tags: @product
1:25.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 51.674
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 24.050
And I take note of which tps features are available 0.675
Then a Tails persistence partition exists on USB drive "old" 0.677
And I shutdown Tails and wait for the computer to power off 8.167
After features/support/hooks.rb:331 0.309
After features/support/hooks.rb:100 0.020
Tags: @product
1:17.023
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.648
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.080
When I write some files expected to persist 1.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.702
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 2.656
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.736
After features/support/hooks.rb:331 0.260
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.075
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.244
And I log in to a new session 10.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.667
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.133
Then the running Tails is installed on USB drive "to_upgrade" 15.170
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 2.257
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.307
Then all tps features from the old Tails version are active 0.922
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.526
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 1.909
After features/support/hooks.rb:331 0.659
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:47.993
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.048
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.315
When the network is plugged 0.015
And Tor is ready 12.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.075
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.315
Given I shutdown Tails and wait for the computer to power off 9.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.623
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.204
When the network is plugged 0.016
And Tor is ready 40.887
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.783
Given I shutdown Tails and wait for the computer to power off 7.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.278
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 0.979
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.011
And Tor is ready 10.794
Then the Upgrader considers the system as up-to-date 0.092
# 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 3.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:331 0.885
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
18.569
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.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.827
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.009
After features/support/hooks.rb:331 0.626
After features/support/hooks.rb:100 0.000