Project Number Date
test_Tails_ISO_stable 6352 05 May 2026, 12:50

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:8.004 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:15.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.794
When I start Tails from USB drive "old" with network unplugged 55.900
Then the boot device has safe access rights 2.842
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 3.720
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 56.412
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 25.899
And I take note of which tps features are available 0.718
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 7.205
After features/support/hooks.rb:331 0.304
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.921
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.183
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.119
When I write some files expected to persist 1.241
# 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.395
And all persistent directories from the old Tails version have safe access rights 2.102
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 8.465
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.766
After features/support/hooks.rb:331 0.399
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 8.795
And I log in to a new session 13.227
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.482
And I plug USB drive "to_upgrade" 2.307
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.364
Then the running Tails is installed on USB drive "to_upgrade" 18.396
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 2.457
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.039
Then all tps features from the old Tails version are active 1.275
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 2.916
And the expected persistent files created with the old Tails version are present in the filesystem 1.166
And all persistent directories from the old Tails version have safe access rights 1.945
After features/support/hooks.rb:331 0.537
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:50.262
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.649
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.046
And Tor is ready 21.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.909
Given I shutdown Tails and wait for the computer to power off 20.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.642
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.130
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.186
When the network is plugged 0.015
And Tor is ready 22.829
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.340
Given I shutdown Tails and wait for the computer to power off 12.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.897
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.018
And Tor is ready 22.223
Then the Upgrader considers the system as up-to-date 0.116
# 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.391
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.446
After features/support/hooks.rb:331 0.737
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
27.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.033
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.860
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 1.034
After features/support/hooks.rb:100 0.000