Project Number Date
test_Tails_ISO_devel 4540 10 Aug 2026, 14:18

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:54.618 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:18.247
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.922
When I start Tails from USB drive "old" with network unplugged 1:0.309
Then the boot device has safe access rights 2.235
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.319
After features/support/hooks.rb:108 0.006
Tags: @product
1:19.200
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 46.716
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 22.812
And I take note of which tps features are available 6.249
Then a Tails persistence partition exists on USB drive "old" 0.502
And I shutdown Tails and wait for the computer to power off 2.557
After features/support/hooks.rb:339 0.202
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.405
Then Tails is running from USB drive "old" 0.333
And all tps features are active 8.944
When I write some files expected to persist 1.478
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.421
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.237
And I shutdown Tails and wait for the computer to power off 4.142
# 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.950
After features/support/hooks.rb:339 0.301
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.052
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 without a persistent partition and stopped at Tails Greeter's login screen 9.055
And I log in to a new session 13.554
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.655
And I plug USB drive "to_upgrade" 2.174
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.336
Then the running Tails is installed on USB drive "to_upgrade" 19.015
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.630
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.794
Then all tps features from the old Tails version are active 1.174
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.642
And the expected persistent files created with the old Tails version are present in the filesystem 0.991
And all persistent directories from the old Tails version have safe access rights 1.676
After features/support/hooks.rb:339 0.621
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:35.165
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 with a persistent partition enabled and logged in 8.656
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.320
When the network is plugged 0.029
And Tor is ready 13.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.565
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.555
Given I shutdown Tails and wait for the computer to power off 5.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.409
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.944
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.234
When the network is plugged 0.021
And Tor is ready 10.581
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.076
Given I shutdown Tails and wait for the computer to power off 2.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.601
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.244
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.029
And Tor is ready 10.315
Then the Upgrader considers the system as up-to-date 0.107
# 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.708
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.411
After features/support/hooks.rb:339 0.826
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
34.308
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 22.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.650
After features/support/hooks.rb:339 0.901
After features/support/hooks.rb:108 0.000