Project Number Date
test_Tails_ISO_devel 4420 28 May 2026, 11: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 11:43.518 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:10.282
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 13.520
When I start Tails from USB drive "old" with network unplugged 52.265
Then the boot device has safe access rights 2.702
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:335 1.540
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.392
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 56.700
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 26.014
And I take note of which tps features are available 0.331
Then a Tails persistence partition exists on USB drive "old" 0.674
And I shutdown Tails and wait for the computer to power off 4.340
After features/support/hooks.rb:335 0.490
After features/support/hooks.rb:104 0.026
Tags: @product
1:31.102
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.138
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.090
When I write some files expected to persist 1.249
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 2.022
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 8.602
# 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.974
After features/support/hooks.rb:335 0.236
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.590
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 without a persistent partition and stopped at Tails Greeter's login screen 8.553
And I log in to a new session 13.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.880
And I plug USB drive "to_upgrade" 2.305
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.128
Then the running Tails is installed on USB drive "to_upgrade" 16.389
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:335 2.288
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.164
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.419
Then all tps features from the old Tails version are active 1.248
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.481
And the expected persistent files created with the old Tails version are present in the filesystem 1.432
And all persistent directories from the old Tails version have safe access rights 2.210
After features/support/hooks.rb:335 0.623
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:48.840
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 with a persistent partition enabled and logged in 8.502
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.017
And Tor is ready 12.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.697
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.277
Given I shutdown Tails and wait for the computer to power off 9.974
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.918
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.216
When the network is plugged 0.016
And Tor is ready 10.098
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.549
Given I shutdown Tails and wait for the computer to power off 8.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.432
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.268
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.015
And Tor is ready 11.443
Then the Upgrader considers the system as up-to-date 10.650
# 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.285
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:335 0.690
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
20.145
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 9.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.365
After features/support/hooks.rb:335 0.595
After features/support/hooks.rb:104 0.000