Project Number Date
test_Tails_ISO_stable 6027 30 Dec 2025, 11:58

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:42.083 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:54.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 30.886
When I start Tails from USB drive "old" with network unplugged 1:18.617
Then the boot device has safe access rights 2.919
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:331 3.841
After features/support/hooks.rb:100 0.011
Tags: @product
1:43.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:3.544
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 28.870
And I take note of which tps features are available 1.194
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:331 0.454
After features/support/hooks.rb:100 0.009
Tags: @product
1:49.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.483
Then Tails is running from USB drive "old" 0.334
And all tps features are active 4.525
When I write some files expected to persist 1.654
# 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.404
And all persistent directories from the old Tails version have safe access rights 2.410
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 7.586
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.744
After features/support/hooks.rb:331 0.354
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.108
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 20.609
And I log in to a new session 15.860
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.017
And I plug USB drive "to_upgrade" 2.349
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.250
Then the running Tails is installed on USB drive "to_upgrade" 22.652
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 3.903
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.350
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.041
Then all tps features from the old Tails version are active 1.399
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.013
And the expected persistent files created with the old Tails version are present in the filesystem 1.194
And all persistent directories from the old Tails version have safe access rights 2.448
After features/support/hooks.rb:331 0.643
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:28.210
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 17.705
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.092
And Tor is ready 13.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.109
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.129
Given I shutdown Tails and wait for the computer to power off 11.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.383
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.241
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.204
# 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.187
When the network is plugged 0.053
And Tor is ready 11.466
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.660
Given I shutdown Tails and wait for the computer to power off 7.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.471
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.452
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.062
And Tor is ready 12.714
Then the Upgrader considers the system as up-to-date 0.117
# 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.698
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.561
After features/support/hooks.rb:331 1.073
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.147
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 11.020
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 11.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.602
After features/support/hooks.rb:331 0.814
After features/support/hooks.rb:100 0.000