Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 9 13 May 2025, 21:47

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:1.423 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:53.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 1:11.516
When I start Tails from USB drive "old" with network unplugged 1:36.836
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.789
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:25.949
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 31.017
And I take note of which tps features are available 1.820
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.701
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.327
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.525
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.989
When I write some files expected to persist 2.010
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.648
And I take note of which tps features are available 0.394
And I shutdown Tails and wait for the computer to power off 4.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.178
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.762
And I log in to a new session 19.187
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.918
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.246
Then the running Tails is installed on USB drive "to_upgrade" 26.955
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 2.256
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.256
Then all tps features from the old Tails version are active 1.617
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.421
And all persistent directories from the old Tails version have safe access rights 2.381
After features/support/hooks.rb:330 1.192
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:38.580
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 11.485
And no SquashFS delta is installed 0.214
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.520
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.071
And Tor is ready 22.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.250
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.742
Given I shutdown Tails and wait for the computer to power off 8.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.230
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.285
When the network is plugged 0.072
And Tor is ready 18.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.594
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.669
Given I shutdown Tails and wait for the computer to power off 4.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.333
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.082
And Tor is ready 16.411
Then the Upgrader considers the system as up-to-date 0.341
# 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.978
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.661
After features/support/hooks.rb:330 0.693
After features/support/hooks.rb:100 0.055
Tags: @product @automatic_upgrade
39.204
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.387
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 22.613
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.654
After features/support/hooks.rb:330 0.734
After features/support/hooks.rb:100 0.000