Project Number Date
test_Tails_ISO_stable 5990 08 Dec 2025, 08:35

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:47.113 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:5.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.605
When I start Tails from USB drive "old" with network unplugged 1:29.745
Then the boot device has safe access rights 3.303
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:331 3.792
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:29.133
Then Tails is running from USB drive "old" 0.661
And I create a persistent partition 31.286
And I take note of which tps features are available 1.365
Then a Tails persistence partition exists on USB drive "old" 1.155
And I shutdown Tails and wait for the computer to power off 8.311
After features/support/hooks.rb:331 0.356
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.508
Then Tails is running from USB drive "old" 0.682
And all tps features are active 2.088
When I write some files expected to persist 1.800
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.422
And I take note of which tps features are available 0.767
And I shutdown Tails and wait for the computer to power off 3.249
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.728
After features/support/hooks.rb:331 0.454
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.346
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 13.268
And I log in to a new session 20.160
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.255
And I plug USB drive "to_upgrade" 3.545
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.693
Then the running Tails is installed on USB drive "to_upgrade" 23.004
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 8.020
After features/support/hooks.rb:100 0.000
Tags: @product
1:31.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.366
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.850
Then all tps features from the old Tails version are active 2.065
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.616
And all persistent directories from the old Tails version have safe access rights 2.428
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:30.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.087
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.400
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.070
And Tor is ready 14.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.845
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.494
Given I shutdown Tails and wait for the computer to power off 11.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.517
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.479
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.248
When the network is plugged 0.059
And Tor is ready 13.195
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.650
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.684
Given I shutdown Tails and wait for the computer to power off 3.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.436
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.858
And the file system changes introduced in version 6.3~testoverlayfs are present 0.623
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.231
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.067
And Tor is ready 12.022
Then the Upgrader considers the system as up-to-date 0.164
# 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 7.640
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.661
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
25.069
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.818
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 13.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.689
After features/support/hooks.rb:331 1.079
After features/support/hooks.rb:100 0.000