Project Number Date
test_Tails_ISO_devel 4544 12 Aug 2026, 11:22

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 12:8.319 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.665
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.410
When I start Tails from USB drive "old" with network unplugged 1:0.099
Then the boot device has safe access rights 2.200
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 3.431
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.261
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 49.582
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 23.883
And I take note of which tps features are available 6.792
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 4.153
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.008
Tags: @product
1:35.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.410
Then Tails is running from USB drive "old" 0.203
And all tps features are active 7.350
When I write some files expected to persist 1.070
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.194
And all persistent directories from the old Tails version have safe access rights 2.145
And I take note of which tps features are available 6.877
And I shutdown Tails and wait for the computer to power off 2.608
# 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.935
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.300
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.205
And I log in to a new session 12.150
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.715
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.319
Then the running Tails is installed on USB drive "to_upgrade" 19.389
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 3.816
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.758
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.418
Then all tps features from the old Tails version are active 1.134
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.155
And the expected persistent files created with the old Tails version are present in the filesystem 0.987
And all persistent directories from the old Tails version have safe access rights 1.748
After features/support/hooks.rb:339 0.880
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
4:7.408
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 21.573
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.274
When the network is plugged 0.024
And Tor is ready 20.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.374
Given I shutdown Tails and wait for the computer to power off 5.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.283
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 11.044
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.178
When the network is plugged 0.030
And Tor is ready 10.455
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.015
Given I shutdown Tails and wait for the computer to power off 2.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.010
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.035
And Tor is ready 10.523
Then the Upgrader considers the system as up-to-date 0.098
# 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.672
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:339 0.991
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.844
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.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.391
After features/support/hooks.rb:339 0.843
After features/support/hooks.rb:108 0.000