Project Number Date
test_Tails_ISO_21322-change-domain-deb.tails.boum.org 3 19 May 2026, 14:24

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:57.228 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:13.004
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.242
When I start Tails from USB drive "old" with network unplugged 53.848
Then the boot device has safe access rights 2.998
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:335 1.587
After features/support/hooks.rb:104 0.008
Tags: @product
1:31.028
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 56.665
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 25.853
And I take note of which tps features are available 0.392
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 7.178
After features/support/hooks.rb:335 0.310
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.876
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.331
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.234
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.009
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 8.417
# 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.542
After features/support/hooks.rb:335 0.426
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.614
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.842
And I log in to a new session 13.230
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.247
Then the running Tails is installed on USB drive "to_upgrade" 16.811
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:335 2.125
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.952
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.314
Then all tps features from the old Tails version are active 1.067
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.390
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:335 0.776
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:51.546
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.936
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.019
And Tor is ready 12.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.394
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.095
Given I shutdown Tails and wait for the computer to power off 10.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.422
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.402
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.200
When the network is plugged 0.021
And Tor is ready 12.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.670
Given I shutdown Tails and wait for the computer to power off 4.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.831
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.191
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.044
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.019
And Tor is ready 10.179
Then the Upgrader considers the system as up-to-date 10.608
# 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.325
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:335 1.128
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
20.204
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.039
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.987
After features/support/hooks.rb:335 0.707
After features/support/hooks.rb:104 0.000