Project Number Date
test_Tails_ISO_devel 3851 03 Jun 2025, 13:39

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:19.274 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:25.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 30.382
When I start Tails from USB drive "old" with network unplugged 1:48.918
Then the boot device has safe access rights 3.759
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.455
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 3.808
After features/support/hooks.rb:100 0.018
Tags: @product
2:24.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:32.078
Then Tails is running from USB drive "old" 0.464
And I create a persistent partition 37.328
And I take note of which tps features are available 4.039
Then a Tails persistence partition exists on USB drive "old" 1.393
And I shutdown Tails and wait for the computer to power off 9.024
After features/support/hooks.rb:330 0.309
After features/support/hooks.rb:100 0.022
Tags: @product
3:6.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.347
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.159
Then Tails is running from USB drive "old" 0.791
And all tps features are active 2.184
When I write some files expected to persist 2.901
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.653
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.609
And I take note of which tps features are available 0.603
And I shutdown Tails and wait for the computer to power off 6.664
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.866
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.152
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 without a persistent partition and stopped at Tails Greeter's login screen 12.914
And I log in to a new session 20.153
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.082
And I plug USB drive "to_upgrade" 2.514
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.333
Then the running Tails is installed on USB drive "to_upgrade" 25.729
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 2.489
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.219
Then all tps features from the old Tails version are active 1.697
And Tails is running from USB drive "to_upgrade" 0.415
And the boot device has safe access rights 3.724
And the expected persistent files created with the old Tails version are present in the filesystem 1.800
And all persistent directories from the old Tails version have safe access rights 2.947
After features/support/hooks.rb:330 1.445
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:42.054
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 17.002
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.494
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.446
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.084
And Tor is ready 23.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.201
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.792
Given I shutdown Tails and wait for the computer to power off 11.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.865
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# 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.277
When the network is plugged 0.067
And Tor is ready 17.311
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.641
Given I shutdown Tails and wait for the computer to power off 4.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.290
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.592
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.404
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.117
And Tor is ready 17.954
Then the Upgrader considers the system as up-to-date 0.348
# 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.319
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.669
After features/support/hooks.rb:330 0.709
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.642
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 10.278
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.626
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.150
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 18.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.348
After features/support/hooks.rb:330 1.030
After features/support/hooks.rb:100 0.000