Project Number Date
test_Tails_ISO_stable 6746 13 Oct 2026, 13:58

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:38.468 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
55.741
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.221
When I start Tails from USB drive "old" with network unplugged 39.193
Then the boot device has safe access rights 1.662
And Tails is running from USB drive "old" 0.177
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.145
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.783
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 46.420
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 22.069
And I take note of which tps features are available 6.037
Then a Tails persistence partition exists on USB drive "old" 0.486
And I shutdown Tails and wait for the computer to power off 3.985
After features/support/hooks.rb:339 0.542
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.252
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.377
Then Tails is running from USB drive "old" 0.255
And all tps features are active 7.036
When I write some files expected to persist 0.997
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.541
And I take note of which tps features are available 5.573
And I shutdown Tails and wait for the computer to power off 2.498
# 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.327
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.887
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 8.149
And I log in to a new session 11.097
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.669
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.372
Then the running Tails is installed on USB drive "to_upgrade" 16.934
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.703
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.199
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.604
Then all tps features from the old Tails version are active 0.967
And Tails is running from USB drive "to_upgrade" 0.164
And the boot device has safe access rights 1.976
And the expected persistent files created with the old Tails version are present in the filesystem 0.863
And all persistent directories from the old Tails version have safe access rights 1.548
After features/support/hooks.rb:339 0.522
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:21.936
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 8.152
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.288
When the network is plugged 0.031
And Tor is ready 12.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.810
Given I shutdown Tails and wait for the computer to power off 5.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.104
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.709
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.087
# 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.154
When the network is plugged 0.031
And Tor is ready 10.623
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.129
Given I shutdown Tails and wait for the computer to power off 3.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.011
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.290
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.143
When the network is plugged 0.051
And Tor is ready 10.096
Then the Upgrader considers the system as up-to-date 0.122
# 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.134
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.879
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
18.138
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.863
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.047
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.849
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.000