Project Number Date
test_Tails_ISO_stable 6412 31 May 2026, 11:23

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:12.569 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:12.269
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.976
When I start Tails from USB drive "old" with network unplugged 55.072
Then the boot device has safe access rights 2.485
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:335 1.373
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.016
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 53.125
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 23.869
And I take note of which tps features are available 0.306
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 7.947
After features/support/hooks.rb:335 0.299
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.908
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.165
When I write some files expected to persist 1.287
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.810
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 7.790
# 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.800
After features/support/hooks.rb:335 0.549
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.872
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.941
And I log in to a new session 12.660
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.751
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.955
Then the running Tails is installed on USB drive "to_upgrade" 14.043
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 1.944
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.135
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.499
Then all tps features from the old Tails version are active 0.885
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.054
And all persistent directories from the old Tails version have safe access rights 1.956
After features/support/hooks.rb:335 0.606
After features/support/hooks.rb:104 0.007
3:33.672
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.015
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.015
And Tor is ready 13.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.040
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.294
Given I shutdown Tails and wait for the computer to power off 9.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.657
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.230
When the network is plugged 0.015
And Tor is ready 9.619
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.217
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.139
Given I shutdown Tails and wait for the computer to power off 7.883
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.639
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.023
And Tor is ready 10.693
Then the Upgrader considers the system as up-to-date 10.526
# 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.100
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:335 0.706
After features/support/hooks.rb:104 0.010
20.854
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.649
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.017
And Tor is ready 9.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.212
After features/support/hooks.rb:335 0.861
After features/support/hooks.rb:104 0.000