Project Number Date
test_Tails_ISO_stable 5754 02 Jul 2025, 10:13

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 21:44.939 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:20.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.958
When I start Tails from USB drive "old" with network unplugged 1:40.084
Then the boot device has safe access rights 3.823
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:330 3.531
After features/support/hooks.rb:100 0.083
Tags: @product
2:29.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:39.333
Then Tails is running from USB drive "old" 0.455
And I create a persistent partition 36.207
And I take note of which tps features are available 2.253
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 10.059
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.009
Tags: @product
3:18.454
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.319
Then Tails is running from USB drive "old" 0.364
And all tps features are active 3.584
When I write some files expected to persist 2.222
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.319
And all persistence configuration files have safe access rights 0.631
And all persistent directories from the old Tails version have safe access rights 3.477
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.162
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.689
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.472
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 11.912
And I log in to a new session 22.498
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.878
And I plug USB drive "to_upgrade" 3.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.974
Then the running Tails is installed on USB drive "to_upgrade" 32.400
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 2.166
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.463
Then all tps features from the old Tails version are active 2.608
And Tails is running from USB drive "to_upgrade" 0.763
And the boot device has safe access rights 4.045
And the expected persistent files created with the old Tails version are present in the filesystem 1.914
And all persistent directories from the old Tails version have safe access rights 2.861
After features/support/hooks.rb:330 1.354
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:30.286
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.931
And no SquashFS delta is installed 0.664
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.526
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.068
And Tor is ready 21.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.139
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.397
Given I shutdown Tails and wait for the computer to power off 10.159
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.952
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.464
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.313
When the network is plugged 0.093
And Tor is ready 19.266
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.228
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.831
Given I shutdown Tails and wait for the computer to power off 6.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.341
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.944
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.124
# 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.414
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.582
When the network is plugged 0.078
And Tor is ready 24.112
Then the Upgrader considers the system as up-to-date 0.533
# 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 17.079
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.379
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
41.325
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.905
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.602
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 19.605
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.865
After features/support/hooks.rb:330 1.350
After features/support/hooks.rb:100 0.000