Project Number Date
test_Tails_ISO_stable 6230 25 Mar 2026, 11:23

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 13:14.196 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:31.851
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.157
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.965
When I start Tails from USB drive "old" with network unplugged 1:13.347
Then the boot device has safe access rights 2.627
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 3.757
After features/support/hooks.rb:100 0.024
Tags: @product
1:35.786
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 1:0.703
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 25.489
And I take note of which tps features are available 0.715
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 8.070
After features/support/hooks.rb:331 0.137
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.548
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:1.965
Then Tails is running from USB drive "old" 0.217
And all tps features are active 1.249
When I write some files expected to persist 1.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 1.987
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 7.102
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.764
After features/support/hooks.rb:331 0.326
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.742
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 9.046
And I log in to a new session 20.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.842
And I plug USB drive "to_upgrade" 2.857
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.401
Then the running Tails is installed on USB drive "to_upgrade" 16.785
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 6.780
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.304
Then all tps features from the old Tails version are active 0.981
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.724
And the expected persistent files created with the old Tails version are present in the filesystem 1.094
And all persistent directories from the old Tails version have safe access rights 2.113
After features/support/hooks.rb:331 0.816
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.109
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.693
And no SquashFS delta is installed 0.119
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.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.017
And Tor is ready 22.689
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.969
Given I shutdown Tails and wait for the computer to power off 14.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.465
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.231
When the network is plugged 0.018
And Tor is ready 20.791
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.357
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.186
Given I shutdown Tails and wait for the computer to power off 17.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.685
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.145
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.016
And Tor is ready 20.327
Then the Upgrader considers the system as up-to-date 0.127
# 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.300
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:331 1.058
After features/support/hooks.rb:100 0.066
Tags: @product @automatic_upgrade
27.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.922
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.012
And Tor is ready 18.881
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
After features/support/hooks.rb:331 0.655
After features/support/hooks.rb:100 0.000