Project Number Date
test_Tails_ISO_21790-tor-0.4.9.13 3 26 Sep 2026, 08:57

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:3.827 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:5.436
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.854
When I start Tails from USB drive "old" with network unplugged 47.610
Then the boot device has safe access rights 2.231
And Tails is running from USB drive "old" 0.174
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.546
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.136
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 47.279
Then Tails is running from USB drive "old" 0.190
And I create a persistent partition 23.381
And I take note of which tps features are available 6.548
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 4.077
After features/support/hooks.rb:339 0.166
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.044
Then Tails is running from USB drive "old" 0.268
And all tps features are active 7.639
When I write some files expected to persist 1.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 1.780
And I take note of which tps features are available 5.945
And I shutdown Tails and wait for the computer to power off 2.554
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.767
After features/support/hooks.rb:339 0.224
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.076
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.561
And I log in to a new session 11.916
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.602
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.553
Then the running Tails is installed on USB drive "to_upgrade" 17.960
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.767
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.455
Then all tps features from the old Tails version are active 1.091
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.199
And the expected persistent files created with the old Tails version are present in the filesystem 0.933
And all persistent directories from the old Tails version have safe access rights 1.582
After features/support/hooks.rb:339 0.550
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:23.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.092
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.033
And Tor is ready 12.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.134
Given I shutdown Tails and wait for the computer to power off 5.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.329
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.695
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.141
When the network is plugged 0.034
And Tor is ready 11.351
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.302
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.735
Given I shutdown Tails and wait for the computer to power off 2.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.362
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.545
And the file system changes introduced in version 6.3~testoverlayfs are present 0.310
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.168
When the network is plugged 0.033
And Tor is ready 10.617
Then the Upgrader considers the system as up-to-date 0.092
# 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 3.124
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.077
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 11.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.321
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.000