Project Number Date
test_Tails_ISO_stable 6473 27 Jun 2026, 11: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:24.090 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
57.844
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.199
When I start Tails from USB drive "old" with network unplugged 40.472
Then the boot device has safe access rights 2.496
And Tails is running from USB drive "old" 0.181
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.257
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 50.948
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 23.458
And I take note of which tps features are available 3.896
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 6.765
After features/support/hooks.rb:339 0.438
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.532
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.954
Then Tails is running from USB drive "old" 0.240
And all tps features are active 4.825
When I write some files expected to persist 1.204
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.285
And all persistent directories from the old Tails version have safe access rights 1.697
And I take note of which tps features are available 3.542
And I shutdown Tails and wait for the computer to power off 7.858
# 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.686
After features/support/hooks.rb:339 0.292
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.858
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.197
And I log in to a new session 11.691
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.759
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.925
Then the running Tails is installed on USB drive "to_upgrade" 14.749
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:339 3.816
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.294
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.783
Then all tps features from the old Tails version are active 0.917
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.408
And the expected persistent files created with the old Tails version are present in the filesystem 1.035
And all persistent directories from the old Tails version have safe access rights 1.859
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.007
3:47.762
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.200
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.033
And Tor is ready 12.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.514
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.605
Given I shutdown Tails and wait for the computer to power off 9.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.863
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
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.140
# 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.022
And Tor is ready 9.565
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.690
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.337
Given I shutdown Tails and wait for the computer to power off 7.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.164
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.445
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.013
And Tor is ready 10.678
Then the Upgrader considers the system as up-to-date 10.505
# 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.318
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 0.708
After features/support/hooks.rb:108 0.011
20.921
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 7.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 11.025
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.408
After features/support/hooks.rb:339 0.859
After features/support/hooks.rb:108 0.000