Project Number Date
test_Tails_ISO_stable 5930 04 Nov 2025, 12:34

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:27.014 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:31.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 49.341
When I start Tails from USB drive "old" with network unplugged 1:37.170
Then the boot device has safe access rights 2.896
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:331 4.991
After features/support/hooks.rb:100 0.029
Tags: @product
2:13.199
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:24.713
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 35.879
And I take note of which tps features are available 2.890
Then a Tails persistence partition exists on USB drive "old" 0.972
And I shutdown Tails and wait for the computer to power off 8.142
After features/support/hooks.rb:331 0.290
After features/support/hooks.rb:100 0.012
Tags: @product
2:6.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.363
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.944
When I write some files expected to persist 1.582
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.259
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 7.570
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.215
After features/support/hooks.rb:331 0.404
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.408
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.590
And I log in to a new session 16.085
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.297
And I plug USB drive "to_upgrade" 2.586
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.817
Then the running Tails is installed on USB drive "to_upgrade" 20.639
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:331 4.214
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.406
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.162
Then all tps features from the old Tails version are active 1.369
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.110
And the expected persistent files created with the old Tails version are present in the filesystem 1.290
And all persistent directories from the old Tails version have safe access rights 2.612
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:51.022
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.915
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.063
And Tor is ready 13.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.655
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.107
Given I shutdown Tails and wait for the computer to power off 11.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.916
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.348
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.174
# 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.210
When the network is plugged 0.049
And Tor is ready 11.021
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.844
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.598
Given I shutdown Tails and wait for the computer to power off 7.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.890
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.981
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.051
And Tor is ready 11.878
Then the Upgrader considers the system as up-to-date 0.264
# 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.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.491
After features/support/hooks.rb:331 1.139
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
23.071
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 10.220
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 10.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.739
After features/support/hooks.rb:331 0.822
After features/support/hooks.rb:100 0.000