Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 12 16 May 2025, 20:55

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:54.712 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.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.833
When I start Tails from USB drive "old" with network unplugged 1:48.478
Then the boot device has safe access rights 3.401
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.539
After features/support/hooks.rb:100 0.047
Tags: @product
2:8.253
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:25.250
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.162
And I take note of which tps features are available 2.348
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.174
After features/support/hooks.rb:330 0.220
After features/support/hooks.rb:100 0.007
Tags: @product
3:10.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.083
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.152
When I write some files expected to persist 1.818
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.571
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.771
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.129
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.398
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.578
And I log in to a new session 18.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.806
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.977
Then the running Tails is installed on USB drive "to_upgrade" 20.266
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 3.661
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.114
Then all tps features from the old Tails version are active 1.779
And Tails is running from USB drive "to_upgrade" 0.381
And the boot device has safe access rights 3.164
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.578
After features/support/hooks.rb:330 0.673
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.090
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.803
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
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.408
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.588
When the network is plugged 0.075
And Tor is ready 22.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.110
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.458
Given I shutdown Tails and wait for the computer to power off 8.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.771
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.142
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.375
When the network is plugged 0.081
And Tor is ready 17.494
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.931
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.153
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.010
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 3.260
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.085
And Tor is ready 20.920
Then the Upgrader considers the system as up-to-date 0.308
# 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.469
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.504
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.024
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.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.142
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 22.060
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.502
After features/support/hooks.rb:330 1.836
After features/support/hooks.rb:100 0.000