Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 1 07 May 2025, 19:34

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:27.843 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:7.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.553
When I start Tails from USB drive "old" with network unplugged 1:31.543
Then the boot device has safe access rights 2.971
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 7.199
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:30.498
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 30.989
And I take note of which tps features are available 1.640
Then a Tails persistence partition exists on USB drive "old" 0.899
And I shutdown Tails and wait for the computer to power off 8.373
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.514
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.930
Then Tails is running from USB drive "old" 0.685
And all tps features are active 1.938
When I write some files expected to persist 1.902
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.319
And all persistence configuration files have safe access rights 0.671
And all persistent directories from the old Tails version have safe access rights 2.644
And I take note of which tps features are available 0.388
And I shutdown Tails and wait for the computer to power off 4.516
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.323
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.889
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 without a persistent partition and stopped at Tails Greeter's login screen 10.289
And I log in to a new session 18.741
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.740
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.748
Then the running Tails is installed on USB drive "to_upgrade" 25.401
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:330 6.738
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.150
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.625
And the expected persistent files created with the old Tails version are present in the filesystem 1.598
And all persistent directories from the old Tails version have safe access rights 2.721
After features/support/hooks.rb:330 1.670
After features/support/hooks.rb:100 0.013
6:36.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.077
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.099
And Tor is ready 21.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.980
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.969
Given I shutdown Tails and wait for the computer to power off 8.565
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.961
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.337
When the network is plugged 0.071
And Tor is ready 15.319
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.012
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.003
Given I shutdown Tails and wait for the computer to power off 4.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.015
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.065
And Tor is ready 20.905
Then the Upgrader considers the system as up-to-date 0.334
# 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 18.213
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.197
After features/support/hooks.rb:330 0.691
After features/support/hooks.rb:100 0.018
38.084
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.314
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.506
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.187
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 20.097
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.768
After features/support/hooks.rb:330 1.645
After features/support/hooks.rb:100 0.000