Project Number Date
test_Tails_ISO_devel 4421 29 May 2026, 11:17

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:31.458 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.846
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.799
When I start Tails from USB drive "old" with network unplugged 47.547
Then the boot device has safe access rights 2.735
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:335 1.222
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.398
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.657
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 25.388
And I take note of which tps features are available 0.362
Then a Tails persistence partition exists on USB drive "old" 0.710
And I shutdown Tails and wait for the computer to power off 6.983
After features/support/hooks.rb:335 0.470
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.129
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.062
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.141
When I write some files expected to persist 1.275
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.285
And all persistent directories from the old Tails version have safe access rights 2.005
And I take note of which tps features are available 0.212
And I shutdown Tails and wait for the computer to power off 4.342
# 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.343
After features/support/hooks.rb:335 0.233
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.387
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.531
And I log in to a new session 12.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.768
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.032
Then the running Tails is installed on USB drive "to_upgrade" 15.757
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:335 2.208
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.233
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.929
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 2.243
After features/support/hooks.rb:335 0.544
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:48.214
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.682
And no SquashFS delta is installed 0.067
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.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.020
And Tor is ready 13.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.673
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.698
Given I shutdown Tails and wait for the computer to power off 10.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.849
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.335
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.223
When the network is plugged 0.022
And Tor is ready 10.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.529
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.807
Given I shutdown Tails and wait for the computer to power off 8.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.641
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.152
And the file system changes introduced in version 6.3~testoverlayfs are present 0.665
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.258
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.015
And Tor is ready 10.421
Then the Upgrader considers the system as up-to-date 10.574
# 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.363
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:335 0.805
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.248
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 7.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
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.044
And Tor is ready 10.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.126
After features/support/hooks.rb:335 1.003
After features/support/hooks.rb:104 0.000