Project Number Date
test_Tails_ISO_stable 6698 28 Sep 2026, 17:13

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:14.076 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:3.163
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.378
When I start Tails from USB drive "old" with network unplugged 45.669
Then the boot device has safe access rights 2.367
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 3.378
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.827
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 47.778
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 22.655
And I take note of which tps features are available 6.562
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 4.002
After features/support/hooks.rb:339 0.480
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.835
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.506
Then Tails is running from USB drive "old" 0.248
And all tps features are active 7.462
When I write some files expected to persist 1.289
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.715
And I take note of which tps features are available 5.775
And I shutdown Tails and wait for the computer to power off 2.607
# 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.672
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.560
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 without a persistent partition and stopped at Tails Greeter's login screen 8.046
And I log in to a new session 11.842
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.581
And I plug USB drive "to_upgrade" 2.292
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.636
Then the running Tails is installed on USB drive "to_upgrade" 18.902
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.655
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.403
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.875
And all persistent directories from the old Tails version have safe access rights 1.551
After features/support/hooks.rb:339 0.441
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:30.362
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.471
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.039
And Tor is ready 13.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.670
Given I shutdown Tails and wait for the computer to power off 5.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.289
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.150
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.032
And Tor is ready 10.661
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.165
Given I shutdown Tails and wait for the computer to power off 4.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.517
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.405
And the file system changes introduced in version 6.3~testoverlayfs are present 0.282
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.036
And Tor is ready 10.451
Then the Upgrader considers the system as up-to-date 0.092
# 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.612
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 1.075
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.082
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.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
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.072
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 10.522
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.910
After features/support/hooks.rb:339 0.653
After features/support/hooks.rb:108 0.000