Project Number Date
test_Tails_ISO_stable 6637 03 Sep 2026, 20:03

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:37.900 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:7.990
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 15.428
When I start Tails from USB drive "old" with network unplugged 48.543
Then the boot device has safe access rights 2.229
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:339 3.591
After features/support/hooks.rb:108 0.008
Tags: @product
1:22.125
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 47.084
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 23.412
And I take note of which tps features are available 6.472
Then a Tails persistence partition exists on USB drive "old" 0.647
And I shutdown Tails and wait for the computer to power off 4.213
After features/support/hooks.rb:339 0.167
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.105
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.023
Then Tails is running from USB drive "old" 0.154
And all tps features are active 6.766
When I write some files expected to persist 1.131
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.627
And I take note of which tps features are available 6.316
And I shutdown Tails and wait for the computer to power off 5.159
# 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.386
After features/support/hooks.rb:339 0.236
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.800
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.414
And I log in to a new session 11.805
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.103
Then the running Tails is installed on USB drive "to_upgrade" 18.328
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 1.778
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.378
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 1.456
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.155
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.456
And the expected persistent files created with the old Tails version are present in the filesystem 0.953
And all persistent directories from the old Tails version have safe access rights 1.960
After features/support/hooks.rb:339 0.842
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:47.092
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.625
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.192
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.044
And Tor is ready 12.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.514
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.894
Given I shutdown Tails and wait for the computer to power off 5.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.452
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.840
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.190
# 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.271
When the network is plugged 0.024
And Tor is ready 10.699
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.890
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.833
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.280
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.372
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.081
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.162
When the network is plugged 0.025
And Tor is ready 10.318
Then the Upgrader considers the system as up-to-date 10.510
# 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.842
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.295
After features/support/hooks.rb:339 1.270
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
19.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.670
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.086
After features/support/hooks.rb:339 0.734
After features/support/hooks.rb:108 0.000