Project Number Date
test_Tails_ISO_stable 5661 19 May 2025, 21:16

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:44.780 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:9.533
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.271
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 35.346
When I start Tails from USB drive "old" with network unplugged 1:28.359
Then the boot device has safe access rights 3.285
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 0.975
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login 1:33.312
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 40.507
And I take note of which tps features are available 9.998
Then a Tails persistence partition exists on USB drive "old" 1.068
And I shutdown Tails and wait for the computer to power off 10.070
After features/support/hooks.rb:330 0.204
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.495
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.476
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.446
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.768
And I take note of which tps features are available 0.879
And I shutdown Tails and wait for the computer to power off 4.405
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.399
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.412
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 11.435
And I log in to a new session 20.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.884
And I plug USB drive "to_upgrade" 2.525
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.359
Then the running Tails is installed on USB drive "to_upgrade" 27.191
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:330 6.756
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.925
Then all tps features from the old Tails version are active 1.764
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 3.585
And the expected persistent files created with the old Tails version are present in the filesystem 1.478
And all persistent directories from the old Tails version have safe access rights 2.461
After features/support/hooks.rb:330 2.068
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
7:23.088
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.898
And no SquashFS delta is installed 0.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.176
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.067
And Tor is ready 25.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.722
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.133
Given I shutdown Tails and wait for the computer to power off 9.088
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.357
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.596
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
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.349
# 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.292
When the network is plugged 0.172
And Tor is ready 19.450
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.757
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.785
Given I shutdown Tails and wait for the computer to power off 4.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.532
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.105
And Tor is ready 18.832
Then the Upgrader considers the system as up-to-date 0.336
# 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 16.414
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.987
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.417
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.243
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.132
And the signing key used by the Upgrader is outdated 0.146
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 21.653
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.786
After features/support/hooks.rb:330 2.163
After features/support/hooks.rb:100 0.000