Project Number Date
test_Tails_ISO_devel 4417 27 May 2026, 11:22

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:2.117 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.817
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.690
When I start Tails from USB drive "old" with network unplugged 46.170
Then the boot device has safe access rights 3.033
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:335 3.839
After features/support/hooks.rb:104 0.020
Tags: @product
1:33.275
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login 57.821
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 26.848
And I take note of which tps features are available 0.374
Then a Tails persistence partition exists on USB drive "old" 0.602
And I shutdown Tails and wait for the computer to power off 7.109
After features/support/hooks.rb:335 0.627
After features/support/hooks.rb:104 0.008
Tags: @product
1:35.906
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.304
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.307
When I write some files expected to persist 1.525
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.631
And I take note of which tps features are available 0.205
And I shutdown Tails and wait for the computer to power off 8.168
# 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.786
After features/support/hooks.rb:335 0.385
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.379
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.248
And I log in to a new session 13.250
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.019
Then the running Tails is installed on USB drive "to_upgrade" 16.534
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:335 2.169
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.970
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.446
Then all tps features from the old Tails version are active 0.963
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.759
And the expected persistent files created with the old Tails version are present in the filesystem 1.223
And all persistent directories from the old Tails version have safe access rights 2.247
After features/support/hooks.rb:335 0.819
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:56.472
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.901
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.022
And Tor is ready 13.748
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.082
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.636
Given I shutdown Tails and wait for the computer to power off 10.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.129
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.282
When the network is plugged 0.067
And Tor is ready 11.339
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.934
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.117
Given I shutdown Tails and wait for the computer to power off 8.097
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.618
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.325
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.021
And Tor is ready 11.791
Then the Upgrader considers the system as up-to-date 10.647
# 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.179
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:335 1.074
After features/support/hooks.rb:104 0.023
Tags: @product @automatic_upgrade
22.297
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.214
After features/support/hooks.rb:335 0.986
After features/support/hooks.rb:104 0.000