Project Number Date
test_Tails_ISO_feature-arti 107 05 Jul 2025, 18:37

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 22:29.656 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:28.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.986
When I start Tails from USB drive "old" with network unplugged 1:48.174
Then the boot device has safe access rights 4.921
And Tails is running from USB drive "old" 0.570
And there is no persistence partition on USB drive "old" 0.122
And process "udev-watchdog" is running 0.187
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.287
After features/support/hooks.rb:330 7.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:40.619
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 35.381
And I take note of which tps features are available 2.443
Then a Tails persistence partition exists on USB drive "old" 0.936
And I shutdown Tails and wait for the computer to power off 8.692
After features/support/hooks.rb:330 0.706
After features/support/hooks.rb:100 0.045
Tags: @product
3:28.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.875
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.813
Then Tails is running from USB drive "old" 0.592
And all tps features are active 5.566
When I write some files expected to persist 2.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.299
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.826
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 6.699
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.828
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.461
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 without a persistent partition and stopped at Tails Greeter's login screen 10.019
And I log in to a new session 22.765
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.589
And I plug USB drive "to_upgrade" 2.759
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.189
Then the running Tails is installed on USB drive "to_upgrade" 26.660
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:330 0.911
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.045
Then all tps features from the old Tails version are active 3.057
And Tails is running from USB drive "to_upgrade" 1.266
And the boot device has safe access rights 4.426
And the expected persistent files created with the old Tails version are present in the filesystem 2.125
And all persistent directories from the old Tails version have safe access rights 2.553
After features/support/hooks.rb:330 1.393
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
7:58.634
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 14.530
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.501
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.572
When the network is plugged 0.066
And Tor is ready 53.575
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.718
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.155
Given I shutdown Tails and wait for the computer to power off 10.856
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.517
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.385
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.326
When the network is plugged 0.096
And Tor is ready 20.532
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.518
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.324
Given I shutdown Tails and wait for the computer to power off 6.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.661
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.943
And the file system changes introduced in version 6.3~testoverlayfs are present 0.878
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.647
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.591
When the network is plugged 0.077
And Tor is ready 21.992
Then the Upgrader considers the system as up-to-date 0.340
# 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 19.408
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.518
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
43.240
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 11.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.167
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.165
And Tor is ready 21.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.212
After features/support/hooks.rb:330 1.510
After features/support/hooks.rb:100 0.000