Project Number Date
test_Tails_ISO_devel 4060 07 Nov 2025, 20:46

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 17:38.527 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:52.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 54.256
When I start Tails from USB drive "old" with network unplugged 1:53.569
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 3.469
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:31.450
Then Tails is running from USB drive "old" 0.752
And I create a persistent partition 28.685
And I take note of which tps features are available 1.172
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 3.739
After features/support/hooks.rb:331 0.442
After features/support/hooks.rb:100 0.018
Tags: @product
2:12.381
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.364
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.162
When I write some files expected to persist 1.650
# 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.449
And all persistent directories from the old Tails version have safe access rights 2.441
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 7.586
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.495
After features/support/hooks.rb:331 0.611
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.010
And I log in to a new session 20.207
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.576
And I plug USB drive "to_upgrade" 3.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.115
Then the running Tails is installed on USB drive "to_upgrade" 20.830
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 3.810
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.071
Then all tps features from the old Tails version are active 1.369
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.272
And the expected persistent files created with the old Tails version are present in the filesystem 1.535
And all persistent directories from the old Tails version have safe access rights 2.313
After features/support/hooks.rb:331 0.708
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
5:6.445
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.649
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.051
And Tor is ready 14.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.569
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.169
Given I shutdown Tails and wait for the computer to power off 11.180
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.362
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.511
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.267
When the network is plugged 0.141
And Tor is ready 11.714
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.795
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.077
Given I shutdown Tails and wait for the computer to power off 8.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.589
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.993
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.137
And Tor is ready 11.988
Then the Upgrader considers the system as up-to-date 0.188
# 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 5.261
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
52.617
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.802
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 40.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
After features/support/hooks.rb:331 1.008
After features/support/hooks.rb:100 0.000