Project Number Date
test_Tails_ISO_stable 6028 31 Dec 2025, 09:06

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 15:15.613 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:57.475
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.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 33.526
When I start Tails from USB drive "old" with network unplugged 1:17.976
Then the boot device has safe access rights 3.759
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.272
After features/support/hooks.rb:331 4.265
After features/support/hooks.rb:100 0.008
Tags: @product
1:55.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:10.866
Then Tails is running from USB drive "old" 0.726
And I create a persistent partition 29.841
And I take note of which tps features are available 4.134
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 9.007
After features/support/hooks.rb:331 0.659
After features/support/hooks.rb:100 0.010
Tags: @product
1:59.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:23.802
Then Tails is running from USB drive "old" 0.325
And all tps features are active 1.959
When I write some files expected to persist 1.721
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.675
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 7.698
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.967
After features/support/hooks.rb:331 0.628
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.609
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 12.522
And I log in to a new session 17.300
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.843
And I plug USB drive "to_upgrade" 3.001
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.294
Then the running Tails is installed on USB drive "to_upgrade" 23.286
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:331 4.118
After features/support/hooks.rb:100 0.000
Tags: @product
1:31.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:22.017
Then all tps features from the old Tails version are active 2.002
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.149
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.459
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.091
Tags: @product @automatic_upgrade
4:31.060
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.039
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.100
And no SquashFS delta is installed 0.072
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.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.080
And Tor is ready 16.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.718
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.483
Given I shutdown Tails and wait for the computer to power off 8.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.547
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.240
# 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.709
When the network is plugged 0.170
And Tor is ready 11.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.642
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.611
Given I shutdown Tails and wait for the computer to power off 6.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.429
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.631
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.060
And Tor is ready 13.295
Then the Upgrader considers the system as up-to-date 0.195
# 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 6.296
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 0.803
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.938
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 with a persistent partition enabled and logged in 11.653
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 10.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.743
After features/support/hooks.rb:331 1.077
After features/support/hooks.rb:100 0.000