Project Number Date
test_Tails_ISO_stable 5657 19 May 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:2.211 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:6.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 32.932
When I start Tails from USB drive "old" with network unplugged 1:27.969
Then the boot device has safe access rights 3.340
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.408
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.586
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:32.262
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 32.004
And I take note of which tps features are available 1.567
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.358
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.016
Tags: @product
3:4.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.244
Then Tails is running from USB drive "old" 0.603
And all tps features are active 2.093
When I write some files expected to persist 2.430
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.458
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 4.093
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.602
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.872
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.380
And I log in to a new session 19.451
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.202
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.774
Then the running Tails is installed on USB drive "to_upgrade" 22.206
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 1.783
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.832
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.931
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.510
And the expected persistent files created with the old Tails version are present in the filesystem 1.515
And all persistent directories from the old Tails version have safe access rights 2.657
After features/support/hooks.rb:330 1.717
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:31.643
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.740
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
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.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.070
And Tor is ready 21.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.130
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.967
Given I shutdown Tails and wait for the computer to power off 10.757
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.509
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.082
And Tor is ready 18.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.767
Given I shutdown Tails and wait for the computer to power off 6.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.262
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.466
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.073
And Tor is ready 19.052
Then the Upgrader considers the system as up-to-date 0.383
# 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.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.631
After features/support/hooks.rb:330 0.783
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
58.815
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 9.715
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 47.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.595
After features/support/hooks.rb:330 0.680
After features/support/hooks.rb:100 0.000