Project Number Date
test_Tails_ISO_tca-misc-improvements 9 16 Apr 2025, 18:14

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:24.845 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:31.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 50.444
When I start Tails from USB drive "old" with network unplugged 1:35.738
Then the boot device has safe access rights 3.008
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 3.749
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:23.861
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 31.082
And I take note of which tps features are available 1.914
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.514
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.877
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.919
When I write some files expected to persist 1.705
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.667
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.265
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.729
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.805
And I log in to a new session 19.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.421
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.965
Then the running Tails is installed on USB drive "to_upgrade" 26.048
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:330 1.967
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.695
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:10.146
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.814
And the expected persistent files created with the old Tails version are present in the filesystem 1.591
And all persistent directories from the old Tails version have safe access rights 2.859
After features/support/hooks.rb:330 1.437
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:18.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.415
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.527
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.544
When the network is plugged 0.074
And Tor is ready 21.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.451
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.529
Given I shutdown Tails and wait for the computer to power off 1:31.712
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.302
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.304
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.073
# 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.309
When the network is plugged 0.070
And Tor is ready 17.047
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.044
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.053
Given I shutdown Tails and wait for the computer to power off 4.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.804
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.099
And Tor is ready 17.417
Then the Upgrader considers the system as up-to-date 10.770
# 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 15.652
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.462
After features/support/hooks.rb:330 0.741
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.658
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 9.678
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.141
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 24.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.753
After features/support/hooks.rb:330 1.389
After features/support/hooks.rb:100 0.000