Project Number Date
test_Tails_ISO_stable 6175 26 Feb 2026, 17:09

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:54.855 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.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 29.701
When I start Tails from USB drive "old" with network unplugged 1:0.751
Then the boot device has safe access rights 3.207
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 1.480
After features/support/hooks.rb:100 0.009
Tags: @product
1:37.365
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:0.764
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 26.906
And I take note of which tps features are available 1.152
Then a Tails persistence partition exists on USB drive "old" 0.642
And I shutdown Tails and wait for the computer to power off 7.462
After features/support/hooks.rb:331 0.559
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.806
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.839
Then Tails is running from USB drive "old" 0.264
And all tps features are active 1.715
When I write some files expected to persist 1.347
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.550
And all persistent directories from the old Tails version have safe access rights 2.162
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 7.502
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.624
After features/support/hooks.rb:331 0.589
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.587
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 without a persistent partition and stopped at Tails Greeter's login screen 11.247
And I log in to a new session 13.107
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.396
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.559
Then the running Tails is installed on USB drive "to_upgrade" 19.445
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:331 1.950
After features/support/hooks.rb:100 0.000
Tags: @product
1:21.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.128
Then all tps features from the old Tails version are active 1.407
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 2.720
And the expected persistent files created with the old Tails version are present in the filesystem 1.285
And all persistent directories from the old Tails version have safe access rights 2.060
After features/support/hooks.rb:331 0.724
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:37.914
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 11.527
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.071
And Tor is ready 44.358
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.548
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.045
Given I shutdown Tails and wait for the computer to power off 20.976
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.759
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.327
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
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.150
# 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.217
When the network is plugged 0.062
And Tor is ready 22.953
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.551
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.081
Given I shutdown Tails and wait for the computer to power off 17.942
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.117
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.271
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.051
And Tor is ready 22.907
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.174
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:331 0.884
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
31.373
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.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 20.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.564
After features/support/hooks.rb:331 1.204
After features/support/hooks.rb:100 0.000