Project Number Date
test_Tails_ISO_devel 4244 21 Feb 2026, 12:02

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 14:49.722 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:35.921
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 30.206
When I start Tails from USB drive "old" with network unplugged 1:0.388
Then the boot device has safe access rights 3.148
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.815
After features/support/hooks.rb:100 0.010
Tags: @product
1:41.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:3.316
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 28.369
And I take note of which tps features are available 1.201
Then a Tails persistence partition exists on USB drive "old" 0.685
And I shutdown Tails and wait for the computer to power off 7.556
After features/support/hooks.rb:331 0.387
After features/support/hooks.rb:100 0.009
Tags: @product
1:42.986
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.816
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.914
When I write some files expected to persist 1.373
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 2.213
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 7.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.737
After features/support/hooks.rb:331 0.416
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.634
And I log in to a new session 12.239
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.549
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.606
Then the running Tails is installed on USB drive "to_upgrade" 18.852
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:331 2.087
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.604
Then all tps features from the old Tails version are active 1.400
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 2.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.276
After features/support/hooks.rb:331 0.965
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:8.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.645
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.086
And Tor is ready 23.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.697
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.068
Given I shutdown Tails and wait for the computer to power off 21.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.564
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.199
# 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.271
When the network is plugged 0.076
And Tor is ready 22.199
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.564
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.328
Given I shutdown Tails and wait for the computer to power off 17.807
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.377
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.976
And the file system changes introduced in version 6.3~testoverlayfs are present 0.413
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.062
And Tor is ready 22.891
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 5.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:331 1.091
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
53.052
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.488
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.048
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 41.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.566
After features/support/hooks.rb:331 1.011
After features/support/hooks.rb:100 0.000