Project Number Date
test_Tails_ISO_stable 6590 18 Aug 2026, 19:00

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:44.787 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:19.703
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.167
When I start Tails from USB drive "old" with network unplugged 1:1.553
Then the boot device has safe access rights 2.148
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.376
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.445
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 50.376
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.808
And I take note of which tps features are available 7.094
Then a Tails persistence partition exists on USB drive "old" 0.584
And I shutdown Tails and wait for the computer to power off 5.241
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.082
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.615
Then Tails is running from USB drive "old" 0.241
And all tps features are active 7.119
When I write some files expected to persist 1.044
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 1.710
And I take note of which tps features are available 6.297
And I shutdown Tails and wait for the computer to power off 3.985
# 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.481
After features/support/hooks.rb:339 0.268
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.825
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.753
And I log in to a new session 12.973
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.648
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.139
Then the running Tails is installed on USB drive "to_upgrade" 18.836
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 2.086
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.758
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.123
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.592
Then all tps features from the old Tails version are active 1.175
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.733
And the expected persistent files created with the old Tails version are present in the filesystem 1.144
And all persistent directories from the old Tails version have safe access rights 1.723
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:34.712
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.696
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
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.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.309
When the network is plugged 0.029
And Tor is ready 13.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.021
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.160
Given I shutdown Tails and wait for the computer to power off 5.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.949
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 10.627
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# 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.189
When the network is plugged 0.036
And Tor is ready 10.679
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.952
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.722
Given I shutdown Tails and wait for the computer to power off 2.779
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.702
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.762
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.035
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.037
And Tor is ready 10.385
Then the Upgrader considers the system as up-to-date 0.116
# 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.551
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.653
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.260
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.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.896
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.000