Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 13 08 Apr 2026, 02:34

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 13:5.674 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:6.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.025
When I start Tails from USB drive "old" with network unplugged 47.188
Then the boot device has safe access rights 3.073
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:331 1.550
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 55.446
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 24.490
And I take note of which tps features are available 0.754
Then a Tails persistence partition exists on USB drive "old" 0.560
And I shutdown Tails and wait for the computer to power off 8.061
After features/support/hooks.rb:331 0.174
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.976
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.120
When I write some files expected to persist 1.521
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.050
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.219
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.797
After features/support/hooks.rb:331 0.515
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.950
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.027
And I log in to a new session 16.859
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.386
Then the running Tails is installed on USB drive "to_upgrade" 16.365
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 3.175
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.904
Then all tps features from the old Tails version are active 1.000
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.602
And the expected persistent files created with the old Tails version are present in the filesystem 1.193
And all persistent directories from the old Tails version have safe access rights 1.968
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
5:1.632
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.051
And no SquashFS delta is installed 0.464
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.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.018
And Tor is ready 22.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.305
Given I shutdown Tails and wait for the computer to power off 16.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.630
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.228
When the network is plugged 0.013
And Tor is ready 40.137
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.723
Given I shutdown Tails and wait for the computer to power off 17.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.205
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.014
And Tor is ready 22.223
Then the Upgrader considers the system as up-to-date 0.099
# 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.698
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.442
After features/support/hooks.rb:331 1.108
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
28.355
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.741
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 19.710
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.415
After features/support/hooks.rb:331 0.931
After features/support/hooks.rb:100 0.000