Project Number Date
test_Tails_ISO_devel 3804 07 May 2025, 13:18

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 20:47.282 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:18.534
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.260
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 31.871
When I start Tails from USB drive "old" with network unplugged 1:40.715
Then the boot device has safe access rights 3.501
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 9.728
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:40.104
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 34.035
And I take note of which tps features are available 2.556
Then a Tails persistence partition exists on USB drive "old" 1.048
And I shutdown Tails and wait for the computer to power off 9.460
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.012
Tags: @product
3:6.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.981
Then Tails is running from USB drive "old" 0.477
And all tps features are active 2.595
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.650
And I take note of which tps features are available 0.545
And I shutdown Tails and wait for the computer to power off 4.578
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.581
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.446
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 13.095
And I log in to a new session 20.935
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.898
And I plug USB drive "to_upgrade" 2.603
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.161
Then the running Tails is installed on USB drive "to_upgrade" 28.271
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:330 2.623
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.793
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.267
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.360
Then all tps features from the old Tails version are active 2.070
And Tails is running from USB drive "to_upgrade" 0.420
And the boot device has safe access rights 4.429
And the expected persistent files created with the old Tails version are present in the filesystem 1.591
And all persistent directories from the old Tails version have safe access rights 2.652
After features/support/hooks.rb:330 1.389
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:5.611
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.393
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.649
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.065
And Tor is ready 21.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.393
Given I shutdown Tails and wait for the computer to power off 8.812
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.096
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.373
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.263
When the network is plugged 0.080
And Tor is ready 25.239
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.166
Given I shutdown Tails and wait for the computer to power off 4.946
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.724
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.211
And the file system changes introduced in version 6.3~testoverlayfs are present 1.417
And only the 6.3~testoverlayfs SquashFS delta is installed 0.849
# 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.598
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.097
And Tor is ready 19.785
Then the Upgrader considers the system as up-to-date 0.335
# 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.283
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.898
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.651
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 10.686
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.141
And Tor is ready 19.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.080
After features/support/hooks.rb:330 0.964
After features/support/hooks.rb:100 0.000