Project Number Date
test_Tails_ISO_devel 4461 19 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 12:9.308 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:2.441
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.490
When I start Tails from USB drive "old" with network unplugged 44.096
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.161
After features/support/hooks.rb:108 0.018
Tags: @product
1:30.750
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login 53.787
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 24.636
And I take note of which tps features are available 4.473
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 6.925
After features/support/hooks.rb:339 0.636
After features/support/hooks.rb:108 0.021
Tags: @product
1:42.622
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.248
Then Tails is running from USB drive "old" 0.279
And all tps features are active 4.693
When I write some files expected to persist 1.199
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.876
And I take note of which tps features are available 4.039
And I shutdown Tails and wait for the computer to power off 8.732
# 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.961
After features/support/hooks.rb:339 0.207
After features/support/hooks.rb:108 0.021
Tags: @product
2:12.477
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.281
And I log in to a new session 13.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.821
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.310
Then the running Tails is installed on USB drive "to_upgrade" 16.007
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:339 3.650
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.451
Then all tps features from the old Tails version are active 1.108
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.655
And the expected persistent files created with the old Tails version are present in the filesystem 1.268
And all persistent directories from the old Tails version have safe access rights 2.122
After features/support/hooks.rb:339 0.810
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
4:2.961
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.890
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.018
And Tor is ready 12.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.256
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.941
Given I shutdown Tails and wait for the computer to power off 9.744
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.798
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.887
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.217
When the network is plugged 0.016
And Tor is ready 11.174
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.215
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.993
Given I shutdown Tails and wait for the computer to power off 8.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.189
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.014
And Tor is ready 10.117
Then the Upgrader considers the system as up-to-date 10.536
# 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.332
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.433
After features/support/hooks.rb:339 1.180
After features/support/hooks.rb:108 0.068
Tags: @product @automatic_upgrade
21.009
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.815
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.257
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.587
After features/support/hooks.rb:339 0.758
After features/support/hooks.rb:108 0.000