Project Number Date
test_Tails_ISO_stable 6492 08 Jul 2026, 11:42

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.820 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:9.295
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.720
When I start Tails from USB drive "old" with network unplugged 51.034
Then the boot device has safe access rights 2.620
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:339 3.813
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.784
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 55.312
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 25.151
And I take note of which tps features are available 4.401
Then a Tails persistence partition exists on USB drive "old" 0.544
And I shutdown Tails and wait for the computer to power off 8.014
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.014
Tags: @product
1:38.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.626
Then Tails is running from USB drive "old" 0.280
And all tps features are active 5.243
When I write some files expected to persist 1.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.304
And all persistent directories from the old Tails version have safe access rights 1.849
And I take note of which tps features are available 3.872
And I shutdown Tails and wait for the computer to power off 7.084
# 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.221
After features/support/hooks.rb:339 0.328
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.180
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.603
And I log in to a new session 12.847
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.820
And I plug USB drive "to_upgrade" 2.336
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.096
Then the running Tails is installed on USB drive "to_upgrade" 16.204
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 2.025
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.527
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.807
Then all tps features from the old Tails version are active 1.054
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.938
And the expected persistent files created with the old Tails version are present in the filesystem 1.309
And all persistent directories from the old Tails version have safe access rights 2.124
After features/support/hooks.rb:339 0.729
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
4:1.786
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 8.286
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.015
And Tor is ready 14.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.564
Given I shutdown Tails and wait for the computer to power off 9.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.308
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.527
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.316
When the network is plugged 0.033
And Tor is ready 11.548
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.557
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.153
Given I shutdown Tails and wait for the computer to power off 8.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.852
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 5.148
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.187
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.019
And Tor is ready 11.290
Then the Upgrader considers the system as up-to-date 10.531
# 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.399
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.737
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.183
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.416
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.468
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.000