Project Number Date
test_Tails_ISO_devel 3733 12 Mar 2025, 01:11

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 18:56.159 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:13.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.425
When I start Tails from USB drive "old" with network unplugged 1:36.197
Then the boot device has safe access rights 3.302
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 3.837
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.170
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 1:22.688
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 32.688
And I take note of which tps features are available 1.840
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.598
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.741
Then Tails is running from USB drive "old" 0.374
And all tps features are active 1.981
When I write some files expected to persist 1.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 3.801
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.468
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.912
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 11.419
And I log in to a new session 18.472
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.698
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.619
Then the running Tails is installed on USB drive "to_upgrade" 23.860
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 1.855
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.256
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.435
Then all tps features from the old Tails version are active 1.676
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.223
And the expected persistent files created with the old Tails version are present in the filesystem 1.688
And all persistent directories from the old Tails version have safe access rights 2.705
After features/support/hooks.rb:330 1.227
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:21.777
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 12.286
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.072
And Tor is ready 21.978
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.359
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.975
Given I shutdown Tails and wait for the computer to power off 8.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.532
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.271
When the network is plugged 0.062
And Tor is ready 18.885
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.258
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.968
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.003
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.065
And Tor is ready 17.304
Then the Upgrader considers the system as up-to-date 0.312
# 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 14.775
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.027
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.163
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 10.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.590
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.587
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.000