Project Number Date
test_Tails_ISO_stable 6324 23 Apr 2026, 07: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 12:56.178 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
58.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.347
When I start Tails from USB drive "old" with network unplugged 40.729
Then the boot device has safe access rights 2.506
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.748
After features/support/hooks.rb:100 0.037
Tags: @product
1:24.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 52.089
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 22.885
And I take note of which tps features are available 0.725
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 8.208
After features/support/hooks.rb:331 0.549
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.417
Then Tails is running from USB drive "old" 0.229
And all tps features are active 1.213
When I write some files expected to persist 1.246
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 1.946
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 7.928
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.216
After features/support/hooks.rb:331 0.323
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.135
And I log in to a new session 16.725
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.858
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.165
Then the running Tails is installed on USB drive "to_upgrade" 15.220
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.891
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.062
Then all tps features from the old Tails version are active 0.877
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 1.996
After features/support/hooks.rb:331 0.860
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:8.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.271
And no SquashFS delta is installed 0.133
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.019
And Tor is ready 33.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.269
Given I shutdown Tails and wait for the computer to power off 22.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.769
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.220
When the network is plugged 0.013
And Tor is ready 40.998
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.694
Given I shutdown Tails and wait for the computer to power off 13.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.940
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.220
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.013
And Tor is ready 20.938
Then the Upgrader considers the system as up-to-date 0.121
# 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 4.362
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:331 1.039
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
27.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.489
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.075
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.000