Project Number Date
test_Tails_ISO_stable 6465 20 Jun 2026, 11:44

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.395 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.180
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.245
When I start Tails from USB drive "old" with network unplugged 59.082
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 3.412
After features/support/hooks.rb:108 0.015
Tags: @product
1:33.575
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.132
And I start Tails from USB drive "old" with network unplugged and I login 55.580
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.581
And I take note of which tps features are available 4.000
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 8.430
After features/support/hooks.rb:339 0.289
After features/support/hooks.rb:108 0.020
Tags: @product
1:36.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.042
Then Tails is running from USB drive "old" 0.285
And all tps features are active 4.944
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.977
And I take note of which tps features are available 4.031
And I shutdown Tails and wait for the computer to power off 4.609
# 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.204
After features/support/hooks.rb:339 0.417
After features/support/hooks.rb:108 0.016
Tags: @product
2:11.909
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.999
And I log in to a new session 12.832
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.841
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.144
Then the running Tails is installed on USB drive "to_upgrade" 15.573
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.269
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.086
Then all tps features from the old Tails version are active 1.035
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.851
And the expected persistent files created with the old Tails version are present in the filesystem 1.165
And all persistent directories from the old Tails version have safe access rights 2.066
After features/support/hooks.rb:339 0.643
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
3:54.497
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.027
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.562
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.024
And Tor is ready 12.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.267
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.903
Given I shutdown Tails and wait for the computer to power off 11.049
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.657
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.221
When the network is plugged 0.021
And Tor is ready 9.792
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.506
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.639
Given I shutdown Tails and wait for the computer to power off 8.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.302
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.492
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.013
And Tor is ready 9.781
Then the Upgrader considers the system as up-to-date 10.544
# 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.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:339 0.929
After features/support/hooks.rb:108 0.056
Tags: @product @automatic_upgrade
20.680
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.778
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.738
After features/support/hooks.rb:339 1.076
After features/support/hooks.rb:108 0.000