Project Number Date
test_Tails_ISO_devel 4660 06 Oct 2026, 11:19

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:17.423 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:15.656
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.340
When I start Tails from USB drive "old" with network unplugged 58.460
Then the boot device has safe access rights 2.091
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.407
After features/support/hooks.rb:108 0.021
Tags: @product
1:19.273
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 "old" with network unplugged and I login 47.901
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 22.733
And I take note of which tps features are available 5.161
Then a Tails persistence partition exists on USB drive "old" 0.516
And I shutdown Tails and wait for the computer to power off 2.669
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.193
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.666
Then Tails is running from USB drive "old" 0.227
And all tps features are active 7.503
When I write some files expected to persist 1.119
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.132
And all persistence configuration files have safe access rights 0.308
And all persistent directories from the old Tails version have safe access rights 1.421
And I take note of which tps features are available 5.927
And I shutdown Tails and wait for the computer to power off 4.112
# 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.697
After features/support/hooks.rb:339 0.143
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.161
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.326
And I log in to a new session 11.361
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.679
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.269
Then the running Tails is installed on USB drive "to_upgrade" 18.084
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.000
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.800
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.241
Then all tps features from the old Tails version are active 1.080
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.007
And all persistent directories from the old Tails version have safe access rights 1.825
After features/support/hooks.rb:339 0.823
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.788
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.175
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.033
And Tor is ready 12.246
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.854
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.527
Given I shutdown Tails and wait for the computer to power off 5.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.230
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.861
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.167
When the network is plugged 0.035
And Tor is ready 10.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.341
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.760
Given I shutdown Tails and wait for the computer to power off 4.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.386
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 9.737
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.025
And Tor is ready 10.151
Then the Upgrader considers the system as up-to-date 0.081
# 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.542
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 0.973
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
18.549
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.783
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 9.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.984
After features/support/hooks.rb:339 0.691
After features/support/hooks.rb:108 0.000