Project Number Date
test_Tails_ISO_stable 5635 08 May 2025, 13:17

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:52.384 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:25.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.081
And I write an old version of the Tails USB image to disk "old" 34.931
When I start Tails from USB drive "old" with network unplugged 1:44.117
Then the boot device has safe access rights 3.861
And Tails is running from USB drive "old" 0.412
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:330 3.873
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:41.655
Then Tails is running from USB drive "old" 0.434
And I create a persistent partition 34.037
And I take note of which tps features are available 2.611
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.909
After features/support/hooks.rb:330 0.212
After features/support/hooks.rb:100 0.009
Tags: @product
3:12.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.726
Then Tails is running from USB drive "old" 1.343
And all tps features are active 3.634
When I write some files expected to persist 3.132
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.482
And all persistent directories from the old Tails version have safe access rights 3.517
And I take note of which tps features are available 0.546
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.684
After features/support/hooks.rb:330 0.267
After features/support/hooks.rb:100 0.017
Tags: @product
2:43.911
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.400
And I log in to a new session 21.672
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.809
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.085
Then the running Tails is installed on USB drive "to_upgrade" 28.950
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:330 3.598
After features/support/hooks.rb:100 0.000
Tags: @product
2:48.659
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.532
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:34.897
Then all tps features from the old Tails version are active 2.269
And Tails is running from USB drive "to_upgrade" 0.402
And the boot device has safe access rights 4.735
And the expected persistent files created with the old Tails version are present in the filesystem 2.257
And all persistent directories from the old Tails version have safe access rights 3.566
After features/support/hooks.rb:330 1.886
After features/support/hooks.rb:100 0.065
Tags: @product @automatic_upgrade
8:26.176
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.199
And no SquashFS delta is installed 0.394
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.632
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.614
When the network is plugged 0.122
And Tor is ready 53.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.758
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.455
Given I shutdown Tails and wait for the computer to power off 11.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:40.118
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 5.455
And the file system changes introduced in version 6.2~testoverlayfs are present 0.411
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.353
When the network is plugged 0.256
And Tor is ready 22.472
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.859
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.384
Given I shutdown Tails and wait for the computer to power off 8.932
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.723
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 9.486
And the file system changes introduced in version 6.3~testoverlayfs are present 0.593
And only the 6.3~testoverlayfs SquashFS delta is installed 0.117
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 1.085
And Tor is ready 17.821
Then the Upgrader considers the system as up-to-date 0.346
# 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.342
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.125
After features/support/hooks.rb:330 1.081
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
46.544
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 13.723
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.635
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.141
But a current signing key is available on our website 0.000
When the network is plugged 0.131
And Tor is ready 23.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.078
After features/support/hooks.rb:330 2.173
After features/support/hooks.rb:100 0.000