Project Number Date
test_Tails_ISO_stable 6006 13 Dec 2025, 12:56

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 14:17.005 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:47.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.382
When I start Tails from USB drive "old" with network unplugged 1:10.752
Then the boot device has safe access rights 3.302
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:331 3.609
After features/support/hooks.rb:100 0.009
Tags: @product
1:42.229
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:5.240
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 29.555
And I take note of which tps features are available 1.245
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 4.921
After features/support/hooks.rb:331 0.261
After features/support/hooks.rb:100 0.008
Tags: @product
1:51.824
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.914
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.790
When I write some files expected to persist 1.694
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.400
And I take note of which tps features are available 0.574
And I shutdown Tails and wait for the computer to power off 8.070
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.355
After features/support/hooks.rb:331 0.592
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.087
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 13.484
And I log in to a new session 17.530
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.302
And I plug USB drive "to_upgrade" 2.773
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.525
Then the running Tails is installed on USB drive "to_upgrade" 21.067
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 3.880
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.782
Then all tps features from the old Tails version are active 1.800
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.115
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.158
After features/support/hooks.rb:331 1.067
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:22.809
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 15.065
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.054
And Tor is ready 15.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.720
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.588
Given I shutdown Tails and wait for the computer to power off 12.676
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.429
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.203
# 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.296
When the network is plugged 0.061
And Tor is ready 11.344
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.690
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.833
Given I shutdown Tails and wait for the computer to power off 4.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.268
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.567
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.183
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.057
And Tor is ready 12.191
Then the Upgrader considers the system as up-to-date 0.175
# 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.988
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.494
After features/support/hooks.rb:331 0.912
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
24.563
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 10.389
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.209
And Tor is ready 10.478
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.126
After features/support/hooks.rb:331 0.820
After features/support/hooks.rb:100 0.000