Project Number Date
test_Tails_ISO_stable 6022 25 Dec 2025, 11: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 13:3.789 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
1:32.057
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 29.922
When I start Tails from USB drive "old" with network unplugged 57.011
Then the boot device has safe access rights 3.083
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 3.857
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 59.593
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 26.676
And I take note of which tps features are available 1.014
Then a Tails persistence partition exists on USB drive "old" 0.684
And I shutdown Tails and wait for the computer to power off 7.457
After features/support/hooks.rb:331 0.630
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.182
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.802
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.189
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 7.486
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.343
After features/support/hooks.rb:331 0.565
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.020
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 without a persistent partition and stopped at Tails Greeter's login screen 11.038
And I log in to a new session 14.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.775
And I plug USB drive "to_upgrade" 2.800
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.070
Then the running Tails is installed on USB drive "to_upgrade" 19.174
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:331 3.729
After features/support/hooks.rb:100 0.000
Tags: @product
1:21.728
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.151
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.793
Then all tps features from the old Tails version are active 1.315
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 2.796
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 2.166
After features/support/hooks.rb:331 0.609
After features/support/hooks.rb:100 0.009
4:1.645
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 11.665
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.069
And Tor is ready 13.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.801
Given I shutdown Tails and wait for the computer to power off 12.457
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.651
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.215
When the network is plugged 0.063
And Tor is ready 11.778
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.925
Given I shutdown Tails and wait for the computer to power off 7.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.689
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.059
And Tor is ready 11.634
Then the Upgrader considers the system as up-to-date 0.147
# 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.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:331 1.043
After features/support/hooks.rb:100 0.019
21.614
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 9.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 11.086
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.564
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.000