Project Number Date
test_Tails_ISO_stable 6512 20 Jul 2026, 17:16

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 12:11.670 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:3.584
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.325
When I start Tails from USB drive "old" with network unplugged 44.487
Then the boot device has safe access rights 2.859
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:339 3.548
After features/support/hooks.rb:108 0.008
Tags: @product
1:34.227
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 55.658
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 24.906
And I take note of which tps features are available 4.270
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:339 0.161
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.924
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.962
Then Tails is running from USB drive "old" 0.243
And all tps features are active 5.157
When I write some files expected to persist 1.430
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.145
And I take note of which tps features are available 4.264
And I shutdown Tails and wait for the computer to power off 8.090
# 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.982
After features/support/hooks.rb:339 0.456
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.520
And I log in to a new session 13.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.058
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.649
Then the running Tails is installed on USB drive "to_upgrade" 18.676
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.584
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.154
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.934
Then all tps features from the old Tails version are active 1.083
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.615
And the expected persistent files created with the old Tails version are present in the filesystem 1.202
And all persistent directories from the old Tails version have safe access rights 1.996
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:56.864
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.113
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.018
And Tor is ready 13.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.767
Given I shutdown Tails and wait for the computer to power off 5.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.562
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.057
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
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.155
# 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.240
When the network is plugged 0.016
And Tor is ready 10.042
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.589
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 4.147
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.560
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.270
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.021
And Tor is ready 11.370
Then the Upgrader considers the system as up-to-date 10.535
# 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 4.392
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:339 1.196
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.073
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.719
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
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.016
And Tor is ready 9.986
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.997
After features/support/hooks.rb:339 0.690
After features/support/hooks.rb:108 0.000