Project Number Date
test_Tails_ISO_stable 6652 09 Sep 2026, 17:33

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:16.205 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.203
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.579
When I start Tails from USB drive "old" with network unplugged 42.657
Then the boot device has safe access rights 2.173
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 1.716
After features/support/hooks.rb:108 0.007
Tags: @product
1:22.184
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 48.419
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 22.276
And I take note of which tps features are available 6.433
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 4.193
After features/support/hooks.rb:339 0.137
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.538
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.033
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.602
When I write some files expected to persist 1.148
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.656
And I take note of which tps features are available 7.158
And I shutdown Tails and wait for the computer to power off 2.645
# 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.464
After features/support/hooks.rb:339 0.273
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.947
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.660
And I log in to a new session 11.734
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.252
Then the running Tails is installed on USB drive "to_upgrade" 19.118
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.675
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.458
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.640
Then all tps features from the old Tails version are active 1.158
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.384
And the expected persistent files created with the old Tails version are present in the filesystem 1.087
And all persistent directories from the old Tails version have safe access rights 1.855
After features/support/hooks.rb:339 0.739
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:36.827
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.532
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.192
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.293
When the network is plugged 0.029
And Tor is ready 12.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.058
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.435
Given I shutdown Tails and wait for the computer to power off 5.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.759
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.547
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.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.196
When the network is plugged 0.035
And Tor is ready 10.523
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.786
Given I shutdown Tails and wait for the computer to power off 4.052
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.793
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.083
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.045
And Tor is ready 10.535
Then the Upgrader considers the system as up-to-date 0.099
# 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.102
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 1.231
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.045
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.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.069
After features/support/hooks.rb:339 0.707
After features/support/hooks.rb:108 0.000