Project Number Date
test_Tails_ISO_stable 5594 24 Apr 2025, 13:19

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 21:9.497 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:28.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.386
And I create a 7200 MiB disk named "old" 0.177
And I plug USB drive "old" 1.193
And I write an old version of the Tails USB image to disk "old" 42.233
When I start Tails from USB drive "old" with network unplugged 1:40.379
Then the boot device has safe access rights 3.535
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 13.559
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.496
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:33.162
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 31.398
And I take note of which tps features are available 2.848
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 8.667
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.546
Then Tails is running from USB drive "old" 0.756
And all tps features are active 2.497
When I write some files expected to persist 2.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.925
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 6.347
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.834
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.217
And I log in to a new session 20.120
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.201
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.597
Then the running Tails is installed on USB drive "to_upgrade" 26.611
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 1.130
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.327
Then all tps features from the old Tails version are active 1.717
And Tails is running from USB drive "to_upgrade" 0.469
And the boot device has safe access rights 4.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.572
And all persistent directories from the old Tails version have safe access rights 2.587
After features/support/hooks.rb:330 1.543
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:26.107
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 12.959
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.573
When the network is plugged 0.077
And Tor is ready 25.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.732
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.608
Given I shutdown Tails and wait for the computer to power off 11.983
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.956
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.447
And only the 6.2~testoverlayfs SquashFS delta is installed 0.124
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.419
# 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.365
When the network is plugged 0.093
And Tor is ready 21.376
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.799
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.784
Given I shutdown Tails and wait for the computer to power off 4.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.457
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.457
And the file system changes introduced in version 6.3~testoverlayfs are present 0.725
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.472
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.414
When the network is plugged 0.149
And Tor is ready 16.353
Then the Upgrader considers the system as up-to-date 10.954
# 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.988
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.667
After features/support/hooks.rb:330 0.851
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
44.574
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 13.480
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.239
And Tor is ready 20.470
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.718
After features/support/hooks.rb:330 0.693
After features/support/hooks.rb:100 0.000