Project Number Date
test_Tails_ISO_21779-fix-korean-input 2 16 Sep 2026, 17:45

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:6.340 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:13.863
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 12.802
When I start Tails from USB drive "old" with network unplugged 57.442
Then the boot device has safe access rights 1.950
And Tails is running from USB drive "old" 0.189
And there is no persistence partition on USB drive "old" 0.029
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.134
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.687
After features/support/hooks.rb:108 0.022
Tags: @product
1:17.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.590
Then Tails is running from USB drive "old" 0.166
And I create a persistent partition 22.036
And I take note of which tps features are available 5.950
Then a Tails persistence partition exists on USB drive "old" 0.491
And I shutdown Tails and wait for the computer to power off 2.531
After features/support/hooks.rb:339 0.470
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.192
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.272
Then Tails is running from USB drive "old" 0.173
And all tps features are active 6.764
When I write some files expected to persist 1.101
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.106
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.478
And I take note of which tps features are available 6.163
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.219
After features/support/hooks.rb:339 0.072
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.422
And I log in to a new session 11.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.645
And I plug USB drive "to_upgrade" 2.344
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.212
Then the running Tails is installed on USB drive "to_upgrade" 17.456
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.103
After features/support/hooks.rb:339 1.997
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.327
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.467
Then all tps features from the old Tails version are active 0.996
And Tails is running from USB drive "to_upgrade" 0.186
And the boot device has safe access rights 2.164
And the expected persistent files created with the old Tails version are present in the filesystem 0.925
And all persistent directories from the old Tails version have safe access rights 1.483
After features/support/hooks.rb:339 0.891
After features/support/hooks.rb:108 0.005
3:19.291
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.044
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.171
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.273
When the network is plugged 0.021
And Tor is ready 12.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.944
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.232
Given I shutdown Tails and wait for the computer to power off 5.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.763
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.813
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.080
# 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.168
When the network is plugged 0.022
And Tor is ready 10.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.934
Given I shutdown Tails and wait for the computer to power off 2.767
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.731
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.975
And the file system changes introduced in version 6.3~testoverlayfs are present 0.275
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.039
And Tor is ready 10.061
Then the Upgrader considers the system as up-to-date 0.112
# 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.145
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.304
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.030
31.448
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 20.787
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
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.034
And Tor is ready 7.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.457
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.000