Project Number Date
test_Tails_ISO_20860-unsafe-browser-desktop-portals 2 08 May 2025, 00:26

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 21:12.919 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:26.624
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 34.066
When I start Tails from USB drive "old" with network unplugged 1:46.912
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.770
After features/support/hooks.rb:100 0.013
Tags: @product
2:16.385
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.594
And I start Tails from USB drive "old" with network unplugged and I login 1:31.103
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 32.953
And I take note of which tps features are available 2.215
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.366
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.060
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.991
Then Tails is running from USB drive "old" 0.371
And all tps features are active 1.972
When I write some files expected to persist 1.769
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.279
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 2.521
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.455
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.007
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 10.730
And I log in to a new session 19.653
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.815
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.765
Then the running Tails is installed on USB drive "to_upgrade" 22.191
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 7.119
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.830
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.884
Then all tps features from the old Tails version are active 1.735
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 4.013
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.958
After features/support/hooks.rb:330 1.437
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:45.985
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 11.801
And no SquashFS delta is installed 0.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.585
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.588
When the network is plugged 0.073
And Tor is ready 22.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.734
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.436
Given I shutdown Tails and wait for the computer to power off 8.846
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.143
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.394
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.379
# 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.325
When the network is plugged 0.407
And Tor is ready 20.366
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.285
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.123
Given I shutdown Tails and wait for the computer to power off 6.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.953
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.630
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.398
And Tor is ready 20.897
Then the Upgrader considers the system as up-to-date 11.014
# 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.152
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.711
After features/support/hooks.rb:330 1.052
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
42.026
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.703
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 23.189
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.480
After features/support/hooks.rb:330 0.926
After features/support/hooks.rb:100 0.000