Project Number Date
test_Tails_ISO_stable 5713 12 Jun 2025, 17:24

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 19:19.819 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:7.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.595
When I start Tails from USB drive "old" with network unplugged 1:30.786
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 4.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:28.157
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 31.323
And I take note of which tps features are available 2.399
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 9.098
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.199
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.347
Then Tails is running from USB drive "old" 0.424
And all tps features are active 1.905
When I write some files expected to persist 3.107
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.822
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 6.479
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.835
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.892
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 9.558
And I log in to a new session 18.386
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.400
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.128
Then the running Tails is installed on USB drive "to_upgrade" 28.513
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 2.397
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.773
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.246
Then all tps features from the old Tails version are active 1.622
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.572
And the expected persistent files created with the old Tails version are present in the filesystem 1.504
And all persistent directories from the old Tails version have safe access rights 2.315
After features/support/hooks.rb:330 0.919
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:27.253
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 12.337
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.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.650
When the network is plugged 0.068
And Tor is ready 19.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.957
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.635
Given I shutdown Tails and wait for the computer to power off 8.525
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.790
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.445
When the network is plugged 0.118
And Tor is ready 17.241
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.707
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.051
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.422
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.835
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.091
And Tor is ready 18.118
Then the Upgrader considers the system as up-to-date 0.339
# 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 14.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.963
After features/support/hooks.rb:330 1.106
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.920
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 with a persistent partition enabled and logged in 10.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 1.054
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 21.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.906
After features/support/hooks.rb:330 0.906
After features/support/hooks.rb:100 0.000