Project Number Date
test_Tails_ISO_devel 4671 12 Oct 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:50.558 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:17.538
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.355
When I start Tails from USB drive "old" with network unplugged 59.290
Then the boot device has safe access rights 2.143
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.536
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.690
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 48.576
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 23.403
And I take note of which tps features are available 5.714
Then a Tails persistence partition exists on USB drive "old" 0.542
And I shutdown Tails and wait for the computer to power off 4.108
After features/support/hooks.rb:339 0.196
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.413
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.965
Then Tails is running from USB drive "old" 0.277
And all tps features are active 7.700
When I write some files expected to persist 1.292
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.222
And all persistent directories from the old Tails version have safe access rights 1.802
And I take note of which tps features are available 6.980
And I shutdown Tails and wait for the computer to power off 3.952
# 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.913
After features/support/hooks.rb:339 0.424
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.634
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.804
And I log in to a new session 12.382
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.318
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.089
Then the running Tails is installed on USB drive "to_upgrade" 19.107
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.522
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.119
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.581
Then all tps features from the old Tails version are active 1.362
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.083
And all persistent directories from the old Tails version have safe access rights 1.727
After features/support/hooks.rb:339 0.682
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.085
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.691
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
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.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.369
When the network is plugged 0.037
And Tor is ready 13.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.334
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.196
Given I shutdown Tails and wait for the computer to power off 5.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.157
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 12.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.188
When the network is plugged 0.027
And Tor is ready 10.490
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.954
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.969
Given I shutdown Tails and wait for the computer to power off 3.917
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.139
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.846
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.196
When the network is plugged 0.033
And Tor is ready 10.998
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 3.595
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.310
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.673
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.385
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 1.540
And Tor is ready 8.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.328
After features/support/hooks.rb:339 1.044
After features/support/hooks.rb:108 0.000