Project Number Date
test_Tails_ISO_devel 4222 10 Feb 2026, 04:07

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:44.232 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:4.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 15.298
When I start Tails from USB drive "old" with network unplugged 44.654
Then the boot device has safe access rights 3.004
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:331 1.644
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.477
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 57.276
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 26.580
And I take note of which tps features are available 0.752
Then a Tails persistence partition exists on USB drive "old" 0.623
And I shutdown Tails and wait for the computer to power off 6.915
After features/support/hooks.rb:331 0.373
After features/support/hooks.rb:100 0.006
Tags: @product
1:34.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.672
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.641
When I write some files expected to persist 1.775
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 2.330
And I take note of which tps features are available 0.298
And I shutdown Tails and wait for the computer to power off 7.973
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.699
After features/support/hooks.rb:331 0.375
After features/support/hooks.rb:100 0.006
Tags: @product
2:19.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.017
And I log in to a new session 14.301
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.507
Then the running Tails is installed on USB drive "to_upgrade" 18.812
And I unplug USB drive "to_upgrade" 0.165
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:331 6.534
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.852
Then all tps features from the old Tails version are active 1.090
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 3.015
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 1.955
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
4:32.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.647
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.017
And Tor is ready 14.376
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.462
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.611
Given I shutdown Tails and wait for the computer to power off 14.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.811
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.476
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.257
When the network is plugged 0.018
And Tor is ready 39.671
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.141
Given I shutdown Tails and wait for the computer to power off 8.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.532
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.285
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.015
And Tor is ready 11.874
Then the Upgrader considers the system as up-to-date 0.124
# 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 5.069
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.618
After features/support/hooks.rb:331 0.822
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
21.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.695
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
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.015
And Tor is ready 11.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.719
After features/support/hooks.rb:331 0.983
After features/support/hooks.rb:100 0.000