Project Number Date
test_Tails_ISO_stable 5939 09 Nov 2025, 12:06

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 15:54.567 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:11.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 40.729
When I start Tails from USB drive "old" with network unplugged 1:26.095
Then the boot device has safe access rights 2.753
And Tails is running from USB drive "old" 0.409
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.681
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login 1:23.603
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 28.893
And I take note of which tps features are available 1.162
Then a Tails persistence partition exists on USB drive "old" 0.682
And I shutdown Tails and wait for the computer to power off 7.559
After features/support/hooks.rb:331 0.590
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.749
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.831
When I write some files expected to persist 1.593
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 2.430
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 7.730
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.120
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.873
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 12.290
And I log in to a new session 16.581
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.405
And I plug USB drive "to_upgrade" 2.626
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.458
Then the running Tails is installed on USB drive "to_upgrade" 20.137
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 4.194
After features/support/hooks.rb:100 0.000
Tags: @product
1:43.456
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:34.569
Then all tps features from the old Tails version are active 1.401
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:331 0.974
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:50.497
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.975
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.429
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.100
And Tor is ready 13.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.719
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.944
Given I shutdown Tails and wait for the computer to power off 9.939
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.978
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.286
When the network is plugged 0.058
And Tor is ready 11.073
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.670
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.798
Given I shutdown Tails and wait for the computer to power off 4.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.389
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.941
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.230
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.052
And Tor is ready 11.663
Then the Upgrader considers the system as up-to-date 0.201
# 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.194
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:331 1.182
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.604
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.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 10.901
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.826
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.000