Project Number Date
test_Tails_ISO_stable 6030 01 Jan 2026, 11:54

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:22.217 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:37.714
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.043
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 31.216
When I start Tails from USB drive "old" with network unplugged 1:0.924
Then the boot device has safe access rights 3.413
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:331 3.707
After features/support/hooks.rb:100 0.009
Tags: @product
1:40.745
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:2.206
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 28.461
And I take note of which tps features are available 1.175
Then a Tails persistence partition exists on USB drive "old" 0.714
And I shutdown Tails and wait for the computer to power off 7.741
After features/support/hooks.rb:331 0.250
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.179
Then Tails is running from USB drive "old" 2.739
And all tps features are active 8.349
When I write some files expected to persist 1.525
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 2.184
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 7.715
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.406
After features/support/hooks.rb:331 0.223
After features/support/hooks.rb:100 0.018
Tags: @product
2:43.985
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 12.687
And I log in to a new session 21.321
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.167
And I plug USB drive "to_upgrade" 3.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.762
Then the running Tails is installed on USB drive "to_upgrade" 20.405
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:331 4.125
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.671
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.399
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.943
Then all tps features from the old Tails version are active 1.788
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.818
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.141
After features/support/hooks.rb:331 0.781
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:15.798
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 16.476
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.055
And Tor is ready 14.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.684
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.030
Given I shutdown Tails and wait for the computer to power off 12.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.198
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.852
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.059
And Tor is ready 12.376
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.807
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.117
Given I shutdown Tails and wait for the computer to power off 3.182
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.168
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.821
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.056
And Tor is ready 12.218
Then the Upgrader considers the system as up-to-date 0.120
# 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.300
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.537
After features/support/hooks.rb:331 0.825
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.995
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.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 11.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.806
After features/support/hooks.rb:331 0.919
After features/support/hooks.rb:100 0.000