Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 6 11 May 2025, 20:48

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:5.956 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:1.191
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.836
When I start Tails from USB drive "old" with network unplugged 1:25.148
Then the boot device has safe access rights 3.861
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 3.790
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:26.313
Then Tails is running from USB drive "old" 0.425
And I create a persistent partition 30.503
And I take note of which tps features are available 2.300
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.283
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.086
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.034
When I write some files expected to persist 1.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 3.628
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.266
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.119
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.569
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 10.371
And I log in to a new session 18.944
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.467
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.436
Then the running Tails is installed on USB drive "to_upgrade" 20.563
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 2.056
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.270
Then all tps features from the old Tails version are active 1.731
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.534
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.505
After features/support/hooks.rb:330 1.243
After features/support/hooks.rb:100 0.009
7:45.283
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 11.697
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.516
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.084
And Tor is ready 21.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.154
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.289
Given I shutdown Tails and wait for the computer to power off 1:18.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.520
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# 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.360
When the network is plugged 0.077
And Tor is ready 18.698
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.570
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.188
Given I shutdown Tails and wait for the computer to power off 4.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.329
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.949
And the file system changes introduced in version 6.3~testoverlayfs are present 0.692
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.068
And Tor is ready 18.013
Then the Upgrader considers the system as up-to-date 0.306
# 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.724
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.712
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.015
38.653
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 with a persistent partition enabled and logged in 10.958
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.565
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.123
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 20.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.311
After features/support/hooks.rb:330 0.800
After features/support/hooks.rb:100 0.000