Project Number Date
test_Tails_ISO_stable 6048 08 Jan 2026, 20:47

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:4.141 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:54.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.291
And I create a 7200 MiB disk named "old" 0.093
And I plug USB drive "old" 1.129
And I write an old version of the Tails USB image to disk "old" 42.408
When I start Tails from USB drive "old" with network unplugged 1:4.929
Then the boot device has safe access rights 4.182
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.315
After features/support/hooks.rb:331 4.021
After features/support/hooks.rb:100 0.009
Tags: @product
1:48.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:7.038
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 31.782
And I take note of which tps features are available 1.165
Then a Tails persistence partition exists on USB drive "old" 0.645
And I shutdown Tails and wait for the computer to power off 7.761
After features/support/hooks.rb:331 0.615
After features/support/hooks.rb:100 0.031
Tags: @product
1:57.334
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.133
Then Tails is running from USB drive "old" 0.399
And all tps features are active 2.103
When I write some files expected to persist 2.016
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.738
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 7.981
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.613
After features/support/hooks.rb:331 0.598
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.565
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 11.632
And I log in to a new session 10.147
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.773
And I plug USB drive "to_upgrade" 3.044
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.437
Then the running Tails is installed on USB drive "to_upgrade" 22.104
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:331 4.022
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:22.325
Then all tps features from the old Tails version are active 2.374
And Tails is running from USB drive "to_upgrade" 0.498
And the boot device has safe access rights 3.903
And the expected persistent files created with the old Tails version are present in the filesystem 1.721
And all persistent directories from the old Tails version have safe access rights 3.159
After features/support/hooks.rb:331 0.736
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:51.703
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 9.703
And no SquashFS delta is installed 0.077
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.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.054
And Tor is ready 14.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.678
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.581
Given I shutdown Tails and wait for the computer to power off 7.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.529
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.420
When the network is plugged 0.112
And Tor is ready 41.794
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.788
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.331
Given I shutdown Tails and wait for the computer to power off 4.801
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.989
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.534
And the file system changes introduced in version 6.3~testoverlayfs are present 0.626
And only the 6.3~testoverlayfs SquashFS delta is installed 0.130
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.718
When the network is plugged 0.070
And Tor is ready 13.392
Then the Upgrader considers the system as up-to-date 0.151
# 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 7.754
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.627
After features/support/hooks.rb:331 1.187
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
23.246
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.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
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.055
And Tor is ready 10.827
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.799
After features/support/hooks.rb:331 1.239
After features/support/hooks.rb:100 0.000