Project Number Date
test_Tails_ISO_devel 4533 06 Aug 2026, 11:20

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.287 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:0.105
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.321
When I start Tails from USB drive "old" with network unplugged 42.741
Then the boot device has safe access rights 2.198
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.422
After features/support/hooks.rb:108 0.009
Tags: @product
1:26.863
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 49.393
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 25.243
And I take note of which tps features are available 7.178
Then a Tails persistence partition exists on USB drive "old" 0.524
And I shutdown Tails and wait for the computer to power off 4.211
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.040
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.760
Then Tails is running from USB drive "old" 0.223
And all tps features are active 7.620
When I write some files expected to persist 1.298
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.148
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 1.859
And I take note of which tps features are available 6.204
And I shutdown Tails and wait for the computer to power off 2.649
# 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.918
After features/support/hooks.rb:339 0.227
After features/support/hooks.rb:108 0.008
Tags: @product
2:13.309
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.530
And I log in to a new session 11.850
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.936
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.913
Then the running Tails is installed on USB drive "to_upgrade" 18.614
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.725
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.937
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.343
Then all tps features from the old Tails version are active 1.200
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.341
And the expected persistent files created with the old Tails version are present in the filesystem 0.916
And all persistent directories from the old Tails version have safe access rights 1.828
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:38.513
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 8.451
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.025
And Tor is ready 11.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.581
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.017
Given I shutdown Tails and wait for the computer to power off 5.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.208
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.184
When the network is plugged 0.022
And Tor is ready 10.430
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.703
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.935
Given I shutdown Tails and wait for the computer to power off 4.220
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.946
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.266
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.080
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.023
And Tor is ready 10.581
Then the Upgrader considers the system as up-to-date 0.091
# 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.417
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 0.811
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
19.517
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.776
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.501
After features/support/hooks.rb:339 0.664
After features/support/hooks.rb:108 0.000