Project Number Date
test_Tails_ISO_stable 5533 26 Mar 2025, 18:45

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 23:39.512 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:10.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 32.925
When I start Tails from USB drive "old" with network unplugged 1:31.382
Then the boot device has safe access rights 3.365
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.387
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:330 0.849
After features/support/hooks.rb:100 0.015
Tags: @product
2:10.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:25.355
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 31.880
And I take note of which tps features are available 2.779
Then a Tails persistence partition exists on USB drive "old" 1.031
And I shutdown Tails and wait for the computer to power off 9.000
After features/support/hooks.rb:330 0.213
After features/support/hooks.rb:100 0.009
Tags: @product
3:15.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.174
Then Tails is running from USB drive "old" 1.091
And all tps features are active 7.314
When I write some files expected to persist 3.407
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.940
And I take note of which tps features are available 0.690
And I shutdown Tails and wait for the computer to power off 6.362
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.987
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.014
Tags: @product
2:56.066
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.397
And I log in to a new session 22.527
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.267
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.884
Then the running Tails is installed on USB drive "to_upgrade" 28.074
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 0.962
After features/support/hooks.rb:100 0.000
Tags: @product
2:49.436
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 1.693
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:37.379
Then all tps features from the old Tails version are active 2.012
And Tails is running from USB drive "to_upgrade" 0.476
And the boot device has safe access rights 3.549
And the expected persistent files created with the old Tails version are present in the filesystem 1.498
And all persistent directories from the old Tails version have safe access rights 2.827
After features/support/hooks.rb:330 1.851
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
9:33.615
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 36.583
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.519
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.650
When the network is plugged 0.099
And Tor is ready 51.410
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.655
Given I shutdown Tails and wait for the computer to power off 1:27.751
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.934
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.751
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.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.335
When the network is plugged 0.088
And Tor is ready 18.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.237
Given I shutdown Tails and wait for the computer to power off 6.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.998
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.259
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.326
When the network is plugged 0.124
And Tor is ready 19.573
Then the Upgrader considers the system as up-to-date 0.311
# 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.520
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.794
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
43.649
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.040
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.604
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the signing key used by the Upgrader is outdated 0.181
But a current signing key is available on our website 0.000
When the network is plugged 0.146
And Tor is ready 22.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.458
After features/support/hooks.rb:330 3.888
After features/support/hooks.rb:100 0.000