Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 10 14 May 2025, 21:00

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 19:58.399 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:11.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.790
When I start Tails from USB drive "old" with network unplugged 1:33.446
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 3.508
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:42.153
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 29.624
And I take note of which tps features are available 2.171
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 8.300
After features/support/hooks.rb:330 0.427
After features/support/hooks.rb:100 0.011
Tags: @product
2:56.461
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.334
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.057
Then Tails is running from USB drive "old" 0.632
And all tps features are active 2.106
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.592
And I take note of which tps features are available 0.580
And I shutdown Tails and wait for the computer to power off 6.593
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.270
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.026
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 11.111
And I log in to a new session 19.536
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.760
Then the running Tails is installed on USB drive "to_upgrade" 27.116
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 1.957
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.685
Then all tps features from the old Tails version are active 1.749
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.381
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 2.308
After features/support/hooks.rb:330 1.353
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:52.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.413
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.419
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.082
And Tor is ready 21.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.674
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.468
Given I shutdown Tails and wait for the computer to power off 8.985
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.443
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.476
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.277
When the network is plugged 0.074
And Tor is ready 17.302
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.806
Given I shutdown Tails and wait for the computer to power off 4.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.346
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.421
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.083
And Tor is ready 16.680
Then the Upgrader considers the system as up-to-date 10.771
# 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 15.893
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.458
After features/support/hooks.rb:330 0.854
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
38.409
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 9.909
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.281
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.238
And Tor is ready 19.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.252
After features/support/hooks.rb:330 0.927
After features/support/hooks.rb:100 0.000