Project Number Date
test_Tails_ISO_stable 5523 20 Mar 2025, 13:28

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:36.764 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:14.486
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.570
When I start Tails from USB drive "old" with network unplugged 1:36.077
Then the boot device has safe access rights 3.382
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:330 3.742
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:31.215
Then Tails is running from USB drive "old" 1.680
And I create a persistent partition 32.908
And I take note of which tps features are available 2.060
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.370
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.347
Then Tails is running from USB drive "old" 0.738
And all tps features are active 3.927
When I write some files expected to persist 2.635
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.504
And I take note of which tps features are available 0.458
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.929
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.401
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 12.432
And I log in to a new session 18.844
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.922
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.653
Then the running Tails is installed on USB drive "to_upgrade" 22.705
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 1.948
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.846
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.063
Then all tps features from the old Tails version are active 1.970
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.173
And the expected persistent files created with the old Tails version are present in the filesystem 1.593
And all persistent directories from the old Tails version have safe access rights 2.491
After features/support/hooks.rb:330 1.756
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:19.427
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 26.135
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.590
When the network is plugged 0.073
And Tor is ready 22.993
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.308
Given I shutdown Tails and wait for the computer to power off 9.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.720
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.448
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.259
When the network is plugged 0.072
And Tor is ready 17.764
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.301
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.231
Given I shutdown Tails and wait for the computer to power off 4.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.820
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.083
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.075
And Tor is ready 49.941
Then the Upgrader considers the system as up-to-date 0.313
# 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.430
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:330 0.998
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
41.504
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.889
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.165
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 22.572
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.168
After features/support/hooks.rb:330 0.960
After features/support/hooks.rb:100 0.000