Project Number Date
test_Tails_ISO_stable 6525 23 Jul 2026, 07:30

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:21.291 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:2.242
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.197
When I start Tails from USB drive "old" with network unplugged 44.750
Then the boot device has safe access rights 2.579
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.852
After features/support/hooks.rb:108 0.018
Tags: @product
1:28.568
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 52.025
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.081
And I take note of which tps features are available 3.650
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 7.941
After features/support/hooks.rb:339 0.323
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.917
Then Tails is running from USB drive "old" 0.202
And all tps features are active 4.486
When I write some files expected to persist 1.184
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.254
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 3.637
And I shutdown Tails and wait for the computer to power off 7.885
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.750
After features/support/hooks.rb:339 0.465
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.231
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.568
And I log in to a new session 12.174
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.724
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.099
Then the running Tails is installed on USB drive "to_upgrade" 14.103
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:339 1.976
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.043
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.140
Then all tps features from the old Tails version are active 0.842
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.292
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.800
After features/support/hooks.rb:339 0.765
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:41.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.940
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.015
And Tor is ready 12.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.617
Given I shutdown Tails and wait for the computer to power off 6.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.649
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 4.823
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# 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.266
When the network is plugged 0.020
And Tor is ready 10.038
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.031
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.278
Given I shutdown Tails and wait for the computer to power off 3.946
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.777
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.386
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.235
When the network is plugged 0.012
And Tor is ready 9.785
Then the Upgrader considers the system as up-to-date 10.531
# 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.740
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 1.117
After features/support/hooks.rb:108 0.048
Tags: @product @automatic_upgrade
19.100
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.380
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 8.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.007
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.000