Project Number Date
test_Tails_ISO_stable 5597 24 Apr 2025, 17:30

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 23:53.046 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
3:46.536
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.264
And I create a 7200 MiB disk named "old" 0.113
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 1:24.650
When I start Tails from USB drive "old" with network unplugged 2:15.537
Then the boot device has safe access rights 3.766
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.771
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.983
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:36.114
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 35.950
And I take note of which tps features are available 6.040
Then a Tails persistence partition exists on USB drive "old" 0.970
And I shutdown Tails and wait for the computer to power off 8.352
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.376
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.951
Then Tails is running from USB drive "old" 0.366
And all tps features are active 2.655
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.674
And I take note of which tps features are available 1.906
And I shutdown Tails and wait for the computer to power off 6.487
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.217
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.702
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 29.042
And I log in to a new session 21.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.141
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.948
Then the running Tails is installed on USB drive "to_upgrade" 29.595
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.965
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.374
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.268
Then all tps features from the old Tails version are active 2.671
And Tails is running from USB drive "to_upgrade" 0.524
And the boot device has safe access rights 5.257
And the expected persistent files created with the old Tails version are present in the filesystem 2.253
And all persistent directories from the old Tails version have safe access rights 3.493
After features/support/hooks.rb:330 1.657
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:49.176
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.203
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.755
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.653
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.642
When the network is plugged 0.189
And Tor is ready 27.915
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.953
Given I shutdown Tails and wait for the computer to power off 11.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.181
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.554
And the file system changes introduced in version 6.2~testoverlayfs are present 0.503
And only the 6.2~testoverlayfs SquashFS delta is installed 0.116
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.346
When the network is plugged 0.118
And Tor is ready 16.249
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.365
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.929
Given I shutdown Tails and wait for the computer to power off 6.600
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.691
Then Tails is running version 6.3~testoverlayfs 0.105
And all tps features are active 5.504
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.104
And Tor is ready 18.353
Then the Upgrader considers the system as up-to-date 11.027
# 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 17.422
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.640
After features/support/hooks.rb:330 0.956
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
45.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 23.723
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.197
After features/support/hooks.rb:330 0.958
After features/support/hooks.rb:100 0.000