Project Number Date
test_Tails_ISO_stable 5742 26 Jun 2025, 17:46

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:37.664 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.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.397
When I start Tails from USB drive "old" with network unplugged 1:43.357
Then the boot device has safe access rights 4.586
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.140
And udev-watchdog is monitoring the correct device 0.404
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 3.559
After features/support/hooks.rb:100 0.018
Tags: @product
2:23.157
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:34.798
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 35.205
And I take note of which tps features are available 2.685
Then a Tails persistence partition exists on USB drive "old" 0.973
And I shutdown Tails and wait for the computer to power off 8.932
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
3:18.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.640
Then Tails is running from USB drive "old" 1.166
And all tps features are active 2.709
When I write some files expected to persist 1.779
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 3.200
And I take note of which tps features are available 0.572
And I shutdown Tails and wait for the computer to power off 7.894
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.590
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.093
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 10.472
And I log in to a new session 23.712
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.654
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.274
Then the running Tails is installed on USB drive "to_upgrade" 30.454
And I unplug USB drive "to_upgrade" 0.680
And I unplug USB drive "__internal" 0.415
After features/support/hooks.rb:330 2.341
After features/support/hooks.rb:100 0.000
Tags: @product
2:43.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.095
Then all tps features from the old Tails version are active 1.974
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 5.501
And the expected persistent files created with the old Tails version are present in the filesystem 2.463
And all persistent directories from the old Tails version have safe access rights 3.355
After features/support/hooks.rb:330 1.457
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:18.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.011
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.917
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.513
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.091
And Tor is ready 22.790
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.799
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.693
Given I shutdown Tails and wait for the computer to power off 8.855
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.840
Then Tails is running version 6.2~testoverlayfs 0.063
And all tps features are active 2.937
And the file system changes introduced in version 6.2~testoverlayfs are present 0.487
And only the 6.2~testoverlayfs SquashFS delta is installed 0.145
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.492
# 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.537
When the network is plugged 0.107
And Tor is ready 23.622
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.136
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.969
Given I shutdown Tails and wait for the computer to power off 6.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.219
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.648
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.071
And Tor is ready 19.004
Then the Upgrader considers the system as up-to-date 0.312
# 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.572
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.811
After features/support/hooks.rb:330 0.761
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
43.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.115
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.208
And the signing key used by the Upgrader is outdated 0.287
But a current signing key is available on our website 0.000
When the network is plugged 0.455
And Tor is ready 23.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.620
After features/support/hooks.rb:330 0.841
After features/support/hooks.rb:100 0.000