Project Number Date
test_Tails_ISO_20036-check-po-msgfmt-ignore-irrelevant-directories 1 25 Jul 2026, 17:27

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:38.545 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:18.377
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.313
When I start Tails from USB drive "old" with network unplugged 1:0.691
Then the boot device has safe access rights 2.614
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.501
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.847
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 53.347
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.643
And I take note of which tps features are available 3.796
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 4.190
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.820
Then Tails is running from USB drive "old" 0.202
And all tps features are active 4.881
When I write some files expected to persist 1.187
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 1.826
And I take note of which tps features are available 3.485
And I shutdown Tails and wait for the computer to power off 4.192
# 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.903
After features/support/hooks.rb:339 0.215
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.216
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.003
And I log in to a new session 12.255
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.513
Then the running Tails is installed on USB drive "to_upgrade" 14.158
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:339 2.493
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.230
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.618
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.594
And the expected persistent files created with the old Tails version are present in the filesystem 0.970
And all persistent directories from the old Tails version have safe access rights 1.735
After features/support/hooks.rb:339 0.475
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
3:42.397
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 with a persistent partition enabled and logged in 7.793
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.296
When the network is plugged 0.013
And Tor is ready 13.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.477
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 5.510
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.181
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.963
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# 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.233
When the network is plugged 0.024
And Tor is ready 9.646
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.530
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.804
Given I shutdown Tails and wait for the computer to power off 4.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.654
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 4.908
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.012
And Tor is ready 9.949
Then the Upgrader considers the system as up-to-date 10.560
# 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.096
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 1.022
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.393
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 with a persistent partition enabled and logged in 7.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.091
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.000