Project Number Date
test_Tails_ISO_stable 6527 23 Jul 2026, 14:14

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:21.145 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:14.082
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.423
When I start Tails from USB drive "old" with network unplugged 54.715
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:339 3.519
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 57.147
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 25.871
And I take note of which tps features are available 4.821
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 4.388
After features/support/hooks.rb:339 0.206
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.425
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.600
Then Tails is running from USB drive "old" 0.255
And all tps features are active 5.819
When I write some files expected to persist 1.402
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 2.084
And I take note of which tps features are available 4.554
And I shutdown Tails and wait for the computer to power off 4.017
# 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" 13.095
After features/support/hooks.rb:339 0.409
After features/support/hooks.rb:108 0.008
Tags: @product
2:13.778
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.022
And I log in to a new session 15.113
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.726
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.345
Then the running Tails is installed on USB drive "to_upgrade" 16.020
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:339 2.364
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.959
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.786
And the expected persistent files created with the old Tails version are present in the filesystem 1.380
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:339 1.015
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
4:1.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.880
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.019
And Tor is ready 13.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.210
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.848
Given I shutdown Tails and wait for the computer to power off 7.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.336
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.218
When the network is plugged 0.018
And Tor is ready 10.043
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.460
Given I shutdown Tails and wait for the computer to power off 4.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.894
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.532
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.016
And Tor is ready 9.999
Then the Upgrader considers the system as up-to-date 10.567
# 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.933
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.462
After features/support/hooks.rb:339 0.810
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
20.181
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.395
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.270
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.150
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.000