Project Number Date
test_Tails_ISO_stable 6051 11 Jan 2026, 11:48

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 13:9.717 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:34.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.193
When I start Tails from USB drive "old" with network unplugged 1:0.001
Then the boot device has safe access rights 2.939
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 3.513
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 58.827
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 28.470
And I take note of which tps features are available 1.134
Then a Tails persistence partition exists on USB drive "old" 0.656
And I shutdown Tails and wait for the computer to power off 7.449
After features/support/hooks.rb:331 0.451
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.443
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.737
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.316
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 3.037
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.416
After features/support/hooks.rb:331 0.445
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.477
And I log in to a new session 9.566
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.327
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.437
Then the running Tails is installed on USB drive "to_upgrade" 17.583
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:331 3.507
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.141
Then all tps features from the old Tails version are active 1.339
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 2.962
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.079
After features/support/hooks.rb:331 1.001
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:24.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.189
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.049
And Tor is ready 41.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.591
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.068
Given I shutdown Tails and wait for the computer to power off 7.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.820
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.974
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# 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.242
When the network is plugged 0.073
And Tor is ready 11.822
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.491
Given I shutdown Tails and wait for the computer to power off 7.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.950
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 1.911
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.076
And Tor is ready 10.397
Then the Upgrader considers the system as up-to-date 10.610
# 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 5.349
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.467
After features/support/hooks.rb:331 0.726
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
19.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
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.055
And Tor is ready 9.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.559
After features/support/hooks.rb:331 0.893
After features/support/hooks.rb:100 0.000