Project Number Date
test_Tails_ISO_stable 6721 05 Oct 2026, 11:39

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:15.676 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:0.379
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.139
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.353
When I start Tails from USB drive "old" with network unplugged 43.029
Then the boot device has safe access rights 2.118
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.694
After features/support/hooks.rb:108 0.041
Tags: @product
1:23.133
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 48.367
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 23.581
And I take note of which tps features are available 6.411
Then a Tails persistence partition exists on USB drive "old" 0.490
And I shutdown Tails and wait for the computer to power off 3.985
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.769
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.987
Then Tails is running from USB drive "old" 0.221
And all tps features are active 7.570
When I write some files expected to persist 1.143
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.103
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.755
And I take note of which tps features are available 6.223
And I shutdown Tails and wait for the computer to power off 2.547
# 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.870
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.387
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.288
And I log in to a new session 12.535
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.619
And I plug USB drive "to_upgrade" 2.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.890
Then the running Tails is installed on USB drive "to_upgrade" 18.620
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.792
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.566
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.395
Then all tps features from the old Tails version are active 1.156
And Tails is running from USB drive "to_upgrade" 0.174
And the boot device has safe access rights 2.081
And the expected persistent files created with the old Tails version are present in the filesystem 0.945
And all persistent directories from the old Tails version have safe access rights 1.722
After features/support/hooks.rb:339 0.629
After features/support/hooks.rb:108 0.042
Tags: @product @automatic_upgrade
3:34.921
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 8.450
And no SquashFS delta is installed 0.072
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.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.037
And Tor is ready 11.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.702
Given I shutdown Tails and wait for the computer to power off 5.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.350
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.024
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.208
When the network is plugged 0.029
And Tor is ready 10.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.296
Given I shutdown Tails and wait for the computer to power off 4.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.151
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.865
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.038
And Tor is ready 10.472
Then the Upgrader considers the system as up-to-date 0.143
# 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.542
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.929
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
19.517
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 with a persistent partition enabled and logged in 7.923
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 10.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.929
After features/support/hooks.rb:339 0.616
After features/support/hooks.rb:108 0.000