Project Number Date
test_Tails_ISO_stable 5707 10 Jun 2025, 18:21

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 24:2.629 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:45.948
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.258
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 1:0.768
When I start Tails from USB drive "old" with network unplugged 1:38.455
Then the boot device has safe access rights 4.159
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:330 4.222
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.063
And I start Tails from USB drive "old" with network unplugged and I login 1:47.964
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 33.846
And I take note of which tps features are available 2.653
Then a Tails persistence partition exists on USB drive "old" 1.034
And I shutdown Tails and wait for the computer to power off 8.811
After features/support/hooks.rb:330 0.208
After features/support/hooks.rb:100 0.012
Tags: @product
3:45.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:59.125
Then Tails is running from USB drive "old" 2.693
And all tps features are active 2.488
When I write some files expected to persist 2.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.648
And all persistent directories from the old Tails version have safe access rights 3.137
And I take note of which tps features are available 0.579
And I shutdown Tails and wait for the computer to power off 6.937
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.631
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.013
Tags: @product
2:59.466
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 without a persistent partition and stopped at Tails Greeter's login screen 18.049
And I log in to a new session 22.174
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.091
And I plug USB drive "to_upgrade" 2.605
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.343
Then the running Tails is installed on USB drive "to_upgrade" 27.750
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 2.940
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.793
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.258
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.522
Then all tps features from the old Tails version are active 2.700
And Tails is running from USB drive "to_upgrade" 0.423
And the boot device has safe access rights 3.881
And the expected persistent files created with the old Tails version are present in the filesystem 1.737
And all persistent directories from the old Tails version have safe access rights 3.268
After features/support/hooks.rb:330 1.720
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
8:8.511
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.290
And no SquashFS delta is installed 0.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.540
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.442
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.094
And Tor is ready 23.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.149
Given I shutdown Tails and wait for the computer to power off 12.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:40.634
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 8.068
And the file system changes introduced in version 6.2~testoverlayfs are present 0.386
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.393
When the network is plugged 0.292
And Tor is ready 17.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.881
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.188
Given I shutdown Tails and wait for the computer to power off 7.105
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.859
Then Tails is running version 6.3~testoverlayfs 0.029
And all tps features are active 6.709
And the file system changes introduced in version 6.3~testoverlayfs are present 0.655
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 1.184
And Tor is ready 19.198
Then the Upgrader considers the system as up-to-date 0.337
# 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 16.550
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.711
After features/support/hooks.rb:330 1.534
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
1:5.169
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.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.623
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 46.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.816
After features/support/hooks.rb:330 1.359
After features/support/hooks.rb:100 0.000