Project Number Date
test_Tails_ISO_devel 4537 10 Aug 2026, 11:17

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:34.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:0.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.843
When I start Tails from USB drive "old" with network unplugged 41.983
Then the boot device has safe access rights 2.447
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.451
After features/support/hooks.rb:108 0.024
Tags: @product
1:25.728
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 50.190
Then Tails is running from USB drive "old" 0.199
And I create a persistent partition 23.524
And I take note of which tps features are available 8.646
Then a Tails persistence partition exists on USB drive "old" 0.494
And I shutdown Tails and wait for the computer to power off 2.584
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.643
Then Tails is running from USB drive "old" 0.313
And all tps features are active 7.965
When I write some files expected to persist 1.393
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.714
And I take note of which tps features are available 7.051
And I shutdown Tails and wait for the computer to power off 4.032
# 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.039
After features/support/hooks.rb:339 0.578
After features/support/hooks.rb:108 0.009
Tags: @product
2:14.033
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.856
And I log in to a new session 11.596
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.720
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.622
Then the running Tails is installed on USB drive "to_upgrade" 18.771
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.631
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.821
Then all tps features from the old Tails version are active 1.172
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.431
And the expected persistent files created with the old Tails version are present in the filesystem 0.909
And all persistent directories from the old Tails version have safe access rights 2.078
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:42.138
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.231
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.301
When the network is plugged 0.028
And Tor is ready 12.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.625
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.297
Given I shutdown Tails and wait for the computer to power off 5.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.873
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.972
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.155
When the network is plugged 0.023
And Tor is ready 10.491
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.327
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.312
Given I shutdown Tails and wait for the computer to power off 3.863
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.698
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.288
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.025
And Tor is ready 10.379
Then the Upgrader considers the system as up-to-date 10.474
# 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.484
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
20.107
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.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 10.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.912
After features/support/hooks.rb:339 0.623
After features/support/hooks.rb:108 0.000