Project Number Date
test_Tails_ISO_21319-thunderbird-153 4 27 Oct 2026, 15:47

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 12:3.847 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:22.986
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.580
When I start Tails from USB drive "old" with network unplugged 1:3.832
Then the boot device has safe access rights 2.421
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.404
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 3.635
After features/support/hooks.rb:108 0.043
Tags: @product
1:30.206
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.126
And I start Tails from USB drive "old" with network unplugged and I login 52.617
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 26.071
And I take note of which tps features are available 6.612
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 3.917
After features/support/hooks.rb:339 0.180
After features/support/hooks.rb:108 0.008
Tags: @product
1:39.728
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.155
Then Tails is running from USB drive "old" 0.185
And all tps features are active 8.893
When I write some files expected to persist 1.588
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.318
And all persistent directories from the old Tails version have safe access rights 1.589
And I take note of which tps features are available 6.109
And I shutdown Tails and wait for the computer to power off 4.202
# 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" 12.250
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.008
Tags: @product
2:16.108
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.354
And I log in to a new session 11.697
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.822
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.713
Then the running Tails is installed on USB drive "to_upgrade" 20.052
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:339 3.780
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.940
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.111
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.386
Then all tps features from the old Tails version are active 1.318
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.729
And the expected persistent files created with the old Tails version are present in the filesystem 1.297
And all persistent directories from the old Tails version have safe access rights 1.843
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.006
3:39.543
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.212
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.542
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.026
And Tor is ready 12.899
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.303
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.762
Given I shutdown Tails and wait for the computer to power off 5.567
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.430
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 9.020
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.189
When the network is plugged 0.051
And Tor is ready 10.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.338
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.972
Given I shutdown Tails and wait for the computer to power off 4.103
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.145
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 8.256
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.033
And Tor is ready 10.407
Then the Upgrader considers the system as up-to-date 0.133
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:339 0.780
After features/support/hooks.rb:108 0.040
19.332
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.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.576
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.000