Project Number Date
test_Tails_ISO_stable 6614 29 Aug 2026, 11:31

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:29.398 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:13.977
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 13.414
When I start Tails from USB drive "old" with network unplugged 56.987
Then the boot device has safe access rights 1.866
And Tails is running from USB drive "old" 0.181
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.591
After features/support/hooks.rb:108 0.018
Tags: @product
1:22.064
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 47.685
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.108
And I take note of which tps features are available 6.283
Then a Tails persistence partition exists on USB drive "old" 0.441
And I shutdown Tails and wait for the computer to power off 4.213
After features/support/hooks.rb:339 0.302
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.069
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.642
Then Tails is running from USB drive "old" 0.248
And all tps features are active 7.584
When I write some files expected to persist 1.185
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.656
And I take note of which tps features are available 6.593
And I shutdown Tails and wait for the computer to power off 4.096
# 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.519
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.792
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.584
And I log in to a new session 10.840
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.610
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.145
Then the running Tails is installed on USB drive "to_upgrade" 18.118
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.567
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.559
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.722
Then all tps features from the old Tails version are active 1.020
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 1.937
And the expected persistent files created with the old Tails version are present in the filesystem 0.890
And all persistent directories from the old Tails version have safe access rights 1.729
After features/support/hooks.rb:339 0.602
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
3:40.189
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.590
And no SquashFS delta is installed 0.066
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.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.033
And Tor is ready 11.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.515
Given I shutdown Tails and wait for the computer to power off 5.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.624
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.371
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.149
When the network is plugged 0.037
And Tor is ready 10.114
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.962
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.647
Given I shutdown Tails and wait for the computer to power off 4.093
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.835
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.637
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.096
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.028
And Tor is ready 9.377
Then the Upgrader considers the system as up-to-date 10.412
# 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.496
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
18.745
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.965
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.509
After features/support/hooks.rb:339 0.947
After features/support/hooks.rb:108 0.000