Project Number Date
test_Tails_ISO_devel 4638 27 Sep 2026, 11:54

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 15:17.409 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
58.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.645
When I start Tails from USB drive "old" with network unplugged 40.128
Then the boot device has safe access rights 2.204
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.674
After features/support/hooks.rb:108 0.035
Tags: @product
1:21.414
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 47.990
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 23.450
And I take note of which tps features are available 6.551
Then a Tails persistence partition exists on USB drive "old" 0.455
And I shutdown Tails and wait for the computer to power off 2.593
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.856
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.994
Then Tails is running from USB drive "old" 0.232
And all tps features are active 7.543
When I write some files expected to persist 1.192
# 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.304
And all persistent directories from the old Tails version have safe access rights 1.680
And I take note of which tps features are available 5.902
And I shutdown Tails and wait for the computer to power off 3.917
# 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.817
After features/support/hooks.rb:339 0.420
After features/support/hooks.rb:108 0.021
Tags: @product
2:11.788
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.316
And I log in to a new session 11.540
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.642
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.845
Then the running Tails is installed on USB drive "to_upgrade" 17.947
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 1.613
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.192
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.039
And the expected persistent files created with the old Tails version are present in the filesystem 0.897
And all persistent directories from the old Tails version have safe access rights 1.691
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
7:40.906
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.925
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.179
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.311
When the network is plugged 0.083
And Tor is ready 11.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4:3.721
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.957
Given I shutdown Tails and wait for the computer to power off 5.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.677
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.156
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.092
# 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.172
When the network is plugged 0.030
And Tor is ready 10.285
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.563
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.995
Given I shutdown Tails and wait for the computer to power off 4.057
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.677
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.052
And the file system changes introduced in version 6.3~testoverlayfs are present 0.304
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.026
And Tor is ready 10.320
Then the Upgrader considers the system as up-to-date 10.413
# 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.200
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.303
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
22.337
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.947
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
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.038
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.061
After features/support/hooks.rb:339 0.778
After features/support/hooks.rb:108 0.000