Project Number Date
test_Tails_ISO_stable 6555 04 Aug 2026, 11:41

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:40.302 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.654
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.313
When I start Tails from USB drive "old" with network unplugged 38.705
Then the boot device has safe access rights 1.883
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.424
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.479
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 45.193
Then Tails is running from USB drive "old" 0.181
And I create a persistent partition 22.801
And I take note of which tps features are available 6.145
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 2.558
After features/support/hooks.rb:339 0.359
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.805
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.865
Then Tails is running from USB drive "old" 0.218
And all tps features are active 6.623
When I write some files expected to persist 0.920
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.237
And all persistent directories from the old Tails version have safe access rights 1.423
And I take note of which tps features are available 5.808
And I shutdown Tails and wait for the computer to power off 2.564
# 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" 10.929
After features/support/hooks.rb:339 0.455
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.956
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.951
And I log in to a new session 10.202
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.675
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.810
Then the running Tails is installed on USB drive "to_upgrade" 16.880
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.584
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.242
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.657
Then all tps features from the old Tails version are active 1.024
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 1.960
And the expected persistent files created with the old Tails version are present in the filesystem 0.857
And all persistent directories from the old Tails version have safe access rights 1.471
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:21.386
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.840
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.037
And Tor is ready 11.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.924
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.843
Given I shutdown Tails and wait for the computer to power off 5.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.074
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 7.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
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.102
# 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.173
When the network is plugged 0.033
And Tor is ready 10.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.910
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.939
Given I shutdown Tails and wait for the computer to power off 2.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.433
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.664
And the file system changes introduced in version 6.3~testoverlayfs are present 0.241
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.087
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.024
And Tor is ready 10.246
Then the Upgrader considers the system as up-to-date 0.106
# 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.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.887
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
24.777
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.546
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 16.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.832
After features/support/hooks.rb:339 0.878
After features/support/hooks.rb:108 0.000