Project Number Date
test_Tails_ISO_devel 4372 03 May 2026, 10:53

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 11:49.032 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
59.836
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.288
When I start Tails from USB drive "old" with network unplugged 42.367
Then the boot device has safe access rights 2.470
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:331 3.833
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.539
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.790
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 23.472
And I take note of which tps features are available 0.642
Then a Tails persistence partition exists on USB drive "old" 0.467
And I shutdown Tails and wait for the computer to power off 7.895
After features/support/hooks.rb:331 0.321
After features/support/hooks.rb:100 0.006
Tags: @product
1:18.785
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.187
Then Tails is running from USB drive "old" 0.215
And all tps features are active 1.096
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 2.646
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.598
After features/support/hooks.rb:331 0.602
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.769
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 7.439
And I log in to a new session 10.885
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.915
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.624
Then the running Tails is installed on USB drive "to_upgrade" 15.368
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 2.031
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.053
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.631
Then all tps features from the old Tails version are active 0.862
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.342
And the expected persistent files created with the old Tails version are present in the filesystem 1.036
And all persistent directories from the old Tails version have safe access rights 1.901
After features/support/hooks.rb:331 0.632
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:27.352
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 8.172
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.018
And Tor is ready 20.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.422
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.317
Given I shutdown Tails and wait for the computer to power off 19.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.446
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.198
When the network is plugged 0.040
And Tor is ready 20.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.723
Given I shutdown Tails and wait for the computer to power off 17.033
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.230
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.306
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.018
And Tor is ready 20.350
Then the Upgrader considers the system as up-to-date 0.140
# 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.228
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:331 1.052
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
23.695
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 7.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 15.858
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.342
After features/support/hooks.rb:331 1.014
After features/support/hooks.rb:100 0.000