Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 3 08 May 2025, 23:28

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:56.516 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:29.976
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 39.202
When I start Tails from USB drive "old" with network unplugged 1:45.233
Then the boot device has safe access rights 3.225
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.816
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:42.497
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 34.439
And I take note of which tps features are available 3.020
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.370
After features/support/hooks.rb:330 0.210
After features/support/hooks.rb:100 0.007
Tags: @product
3:6.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.540
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.524
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.328
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.585
And I take note of which tps features are available 0.592
And I shutdown Tails and wait for the computer to power off 6.563
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.584
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.851
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 without a persistent partition and stopped at Tails Greeter's login screen 15.627
And I log in to a new session 23.185
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.322
And I plug USB drive "to_upgrade" 2.623
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.039
Then the running Tails is installed on USB drive "to_upgrade" 25.579
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 2.114
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.025
Then all tps features from the old Tails version are active 1.876
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.678
And the expected persistent files created with the old Tails version are present in the filesystem 1.607
And all persistent directories from the old Tails version have safe access rights 2.932
After features/support/hooks.rb:330 1.326
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:1.113
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.278
And no SquashFS delta is installed 0.460
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.539
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.063
And Tor is ready 21.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.029
Given I shutdown Tails and wait for the computer to power off 8.887
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.438
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.339
When the network is plugged 0.064
And Tor is ready 20.204
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.483
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.127
Given I shutdown Tails and wait for the computer to power off 4.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.151
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.114
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.079
And Tor is ready 15.748
Then the Upgrader considers the system as up-to-date 10.846
# 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.173
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.686
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.492
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.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 22.025
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.828
After features/support/hooks.rb:330 0.703
After features/support/hooks.rb:100 0.000