Project Number Date
test_Tails_ISO_stable 6632 03 Sep 2026, 11:35

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:15.690 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:9.629
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 14.594
When I start Tails from USB drive "old" with network unplugged 50.960
Then the boot device has safe access rights 2.239
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.443
After features/support/hooks.rb:108 0.028
Tags: @product
1:23.540
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 49.024
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.790
And I take note of which tps features are available 7.252
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 2.573
After features/support/hooks.rb:339 0.327
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.553
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.753
Then Tails is running from USB drive "old" 0.297
And all tps features are active 9.038
When I write some files expected to persist 1.233
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.766
And I take note of which tps features are available 6.993
And I shutdown Tails and wait for the computer to power off 2.679
# 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.269
After features/support/hooks.rb:339 0.253
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.102
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.590
And I log in to a new session 10.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.581
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.734
Then the running Tails is installed on USB drive "to_upgrade" 18.760
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:339 1.785
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.563
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.706
Then all tps features from the old Tails version are active 1.010
And Tails is running from USB drive "to_upgrade" 0.162
And the boot device has safe access rights 2.101
And the expected persistent files created with the old Tails version are present in the filesystem 0.884
And all persistent directories from the old Tails version have safe access rights 1.603
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:26.624
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.169
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.309
When the network is plugged 0.026
And Tor is ready 11.811
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.512
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.737
Given I shutdown Tails and wait for the computer to power off 5.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.184
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.593
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.033
And Tor is ready 10.347
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.474
Given I shutdown Tails and wait for the computer to power off 2.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.531
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.132
And the file system changes introduced in version 6.3~testoverlayfs are present 0.276
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.076
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.034
And Tor is ready 10.247
Then the Upgrader considers the system as up-to-date 0.088
# 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.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 0.700
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.676
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.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.930
After features/support/hooks.rb:339 1.001
After features/support/hooks.rb:108 0.000