Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 8 13 May 2025, 19:38

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:50.204 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:23.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.320
When I start Tails from USB drive "old" with network unplugged 1:48.005
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 0.913
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:28.810
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 31.262
And I take note of which tps features are available 2.072
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 8.504
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.929
Then Tails is running from USB drive "old" 0.929
And all tps features are active 2.134
When I write some files expected to persist 1.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 3.485
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.429
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.539
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 17.105
And I log in to a new session 18.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.210
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.972
Then the running Tails is installed on USB drive "to_upgrade" 23.476
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 3.344
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.502
Then all tps features from the old Tails version are active 1.672
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.389
And the expected persistent files created with the old Tails version are present in the filesystem 1.401
And all persistent directories from the old Tails version have safe access rights 2.354
After features/support/hooks.rb:330 1.295
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:38.305
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 12.765
And no SquashFS delta is installed 0.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.508
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.087
And Tor is ready 22.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.148
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.063
Given I shutdown Tails and wait for the computer to power off 10.955
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.266
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.074
And the file system changes introduced in version 6.2~testoverlayfs are present 0.382
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.445
# 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.380
When the network is plugged 0.068
And Tor is ready 17.516
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.809
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.535
Given I shutdown Tails and wait for the computer to power off 4.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.932
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.234
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.065
And Tor is ready 16.579
Then the Upgrader considers the system as up-to-date 0.339
# 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.414
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.828
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.421
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 9.915
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 22.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.558
After features/support/hooks.rb:330 0.942
After features/support/hooks.rb:100 0.000