Project Number Date
test_Tails_ISO_stable 6615 30 Aug 2026, 11:32

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:9.108 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:5.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.138
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.136
When I start Tails from USB drive "old" with network unplugged 48.117
Then the boot device has safe access rights 2.126
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.149
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.442
After features/support/hooks.rb:108 0.004
Tags: @product
1:21.486
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 47.750
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.474
And I take note of which tps features are available 6.726
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 2.616
After features/support/hooks.rb:339 0.359
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.028
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.026
Then Tails is running from USB drive "old" 0.181
And all tps features are active 6.631
When I write some files expected to persist 1.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.536
And I take note of which tps features are available 5.894
And I shutdown Tails and wait for the computer to power off 2.544
# 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.349
After features/support/hooks.rb:339 0.313
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.001
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.099
And I log in to a new session 10.162
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.684
And I plug USB drive "to_upgrade" 2.295
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.161
Then the running Tails is installed on USB drive "to_upgrade" 18.354
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 3.614
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.373
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.010
Then all tps features from the old Tails version are active 1.332
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.242
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 1.585
After features/support/hooks.rb:339 0.788
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:32.879
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.194
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.027
And Tor is ready 13.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.164
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.137
Given I shutdown Tails and wait for the computer to power off 5.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.423
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.561
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.148
When the network is plugged 0.032
And Tor is ready 11.059
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.337
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.641
Given I shutdown Tails and wait for the computer to power off 4.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.728
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.415
And the file system changes introduced in version 6.3~testoverlayfs are present 0.304
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.060
And Tor is ready 10.590
Then the Upgrader considers the system as up-to-date 0.106
# 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.443
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:339 1.081
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.235
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 7.934
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
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.034
And Tor is ready 9.680
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.263
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.000