Project Number Date
test_Tails_ISO_stable 5924 01 Nov 2025, 11:59

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 16:3.761 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
2:4.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 25.872
When I start Tails from USB drive "old" with network unplugged 1:33.400
Then the boot device has safe access rights 3.010
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 4.022
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:25.212
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 29.321
And I take note of which tps features are available 1.268
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 7.727
After features/support/hooks.rb:331 0.649
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.329
Then Tails is running from USB drive "old" 0.312
And all tps features are active 2.032
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.610
And I shutdown Tails and wait for the computer to power off 7.749
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.357
After features/support/hooks.rb:331 0.346
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.747
And I log in to a new session 16.059
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.366
And I plug USB drive "to_upgrade" 2.705
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.793
Then the running Tails is installed on USB drive "to_upgrade" 19.759
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:331 4.238
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.248
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.257
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.476
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.311
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:2.749
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 12.779
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.085
And Tor is ready 15.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.983
Given I shutdown Tails and wait for the computer to power off 12.887
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.767
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.291
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.255
When the network is plugged 0.092
And Tor is ready 13.043
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.645
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.547
Given I shutdown Tails and wait for the computer to power off 7.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.801
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.359
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.076
And Tor is ready 10.926
Then the Upgrader considers the system as up-to-date 0.259
# 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.206
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:331 1.023
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.414
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 10.223
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 10.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.687
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.000