Project Number Date
test_Tails_ISO_stable 6414 01 Jun 2026, 14: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 10:51.411 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
58.422
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.001
When I start Tails from USB drive "old" with network unplugged 41.153
Then the boot device has safe access rights 2.544
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 1.220
After features/support/hooks.rb:104 0.006
Tags: @product
1:20.251
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 51.214
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.611
And I take note of which tps features are available 0.380
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 4.231
After features/support/hooks.rb:335 0.620
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.302
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.598
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.109
When I write some files expected to persist 1.204
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.318
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 7.896
# 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.757
After features/support/hooks.rb:335 0.518
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.251
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.911
And I log in to a new session 11.379
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.348
Then the running Tails is installed on USB drive "to_upgrade" 14.354
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:335 1.773
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.629
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 59.922
Then all tps features from the old Tails version are active 0.913
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.496
And the expected persistent files created with the old Tails version are present in the filesystem 1.118
And all persistent directories from the old Tails version have safe access rights 1.904
After features/support/hooks.rb:335 0.600
After features/support/hooks.rb:104 0.005
Tags: @product @automatic_upgrade
3:33.344
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.939
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.015
And Tor is ready 13.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.262
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.350
Given I shutdown Tails and wait for the computer to power off 6.823
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.451
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 0.984
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.171
When the network is plugged 0.015
And Tor is ready 10.592
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.449
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.308
Given I shutdown Tails and wait for the computer to power off 7.859
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.225
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.017
And Tor is ready 11.529
Then the Upgrader considers the system as up-to-date 10.596
# 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.918
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:335 1.122
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.209
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.299
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.041
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.230
After features/support/hooks.rb:335 1.009
After features/support/hooks.rb:104 0.000