Project Number Date
test_Tails_ISO_devel 4459 18 Jun 2026, 11:30

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:3.756 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:1.354
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.644
When I start Tails from USB drive "old" with network unplugged 42.575
Then the boot device has safe access rights 3.113
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 3.740
After features/support/hooks.rb:108 0.022
Tags: @product
1:33.101
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 55.422
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 25.269
And I take note of which tps features are available 4.384
Then a Tails persistence partition exists on USB drive "old" 0.598
And I shutdown Tails and wait for the computer to power off 7.038
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.046
Tags: @product
1:40.691
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.068
Then Tails is running from USB drive "old" 0.247
And all tps features are active 5.197
When I write some files expected to persist 1.298
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 2.073
And I take note of which tps features are available 4.425
And I shutdown Tails and wait for the computer to power off 7.137
# 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" 12.481
After features/support/hooks.rb:339 0.218
After features/support/hooks.rb:108 0.022
Tags: @product
2:13.151
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.040
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.830
And I log in to a new session 13.042
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.286
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.618
Then the running Tails is installed on USB drive "to_upgrade" 16.294
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.757
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.414
Then all tps features from the old Tails version are active 1.205
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.632
And the expected persistent files created with the old Tails version are present in the filesystem 1.163
And all persistent directories from the old Tails version have safe access rights 1.955
After features/support/hooks.rb:339 0.949
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:59.692
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.544
And no SquashFS delta is installed 0.081
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.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.387
When the network is plugged 0.035
And Tor is ready 13.158
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.289
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.629
Given I shutdown Tails and wait for the computer to power off 7.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.961
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.693
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.283
When the network is plugged 0.015
And Tor is ready 9.758
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.861
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.873
Given I shutdown Tails and wait for the computer to power off 7.066
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.296
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.014
And Tor is ready 10.154
Then the Upgrader considers the system as up-to-date 10.520
# 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.337
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.069
Tags: @product @automatic_upgrade
20.007
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.287
After features/support/hooks.rb:339 0.738
After features/support/hooks.rb:108 0.000