Project Number Date
test_Tails_ISO_devel 4279 14 Mar 2026, 11:16

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:50.256 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:12.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.291
When I start Tails from USB drive "old" with network unplugged 52.768
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 1.577
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 56.638
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 25.507
And I take note of which tps features are available 0.796
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 4.432
After features/support/hooks.rb:331 0.642
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.230
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.981
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.233
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.293
And all persistence configuration files have safe access rights 0.550
And all persistent directories from the old Tails version have safe access rights 2.295
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 4.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.713
After features/support/hooks.rb:331 0.133
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.860
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.623
And I log in to a new session 11.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.926
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.066
Then the running Tails is installed on USB drive "to_upgrade" 17.157
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 2.285
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.752
Then all tps features from the old Tails version are active 0.944
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.742
And the expected persistent files created with the old Tails version are present in the filesystem 1.269
And all persistent directories from the old Tails version have safe access rights 2.082
After features/support/hooks.rb:331 0.735
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:42.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.149
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.027
And Tor is ready 20.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.452
Given I shutdown Tails and wait for the computer to power off 15.196
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.467
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.185
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.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.198
# 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.240
When the network is plugged 0.016
And Tor is ready 20.577
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.416
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.820
Given I shutdown Tails and wait for the computer to power off 18.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.222
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.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.022
And Tor is ready 21.378
Then the Upgrader considers the system as up-to-date 0.127
# 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.970
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.567
After features/support/hooks.rb:331 1.141
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
28.754
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.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 19.683
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
After features/support/hooks.rb:331 1.055
After features/support/hooks.rb:100 0.000