Project Number Date
test_Tails_ISO_devel 4483 06 Jul 2026, 11:29

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:19.530 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:13.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 14.079
When I start Tails from USB drive "old" with network unplugged 54.789
Then the boot device has safe access rights 2.791
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.724
After features/support/hooks.rb:108 0.014
Tags: @product
1:34.071
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 55.994
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.534
And I take note of which tps features are available 4.783
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 6.893
After features/support/hooks.rb:339 0.310
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.832
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.868
Then Tails is running from USB drive "old" 0.261
And all tps features are active 5.923
When I write some files expected to persist 1.512
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 2.159
And I take note of which tps features are available 4.292
And I shutdown Tails and wait for the computer to power off 4.355
# 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.866
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.833
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.130
And I log in to a new session 14.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.825
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.572
Then the running Tails is installed on USB drive "to_upgrade" 15.822
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:339 2.297
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.292
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.178
Then all tps features from the old Tails version are active 0.918
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.466
And the expected persistent files created with the old Tails version are present in the filesystem 1.286
And all persistent directories from the old Tails version have safe access rights 2.149
After features/support/hooks.rb:339 0.948
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:4.809
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.812
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.018
And Tor is ready 12.881
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.788
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.321
Given I shutdown Tails and wait for the computer to power off 10.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.245
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.810
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.230
When the network is plugged 0.014
And Tor is ready 11.269
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.298
Given I shutdown Tails and wait for the computer to power off 8.406
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.674
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.929
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.015
And Tor is ready 10.447
Then the Upgrader considers the system as up-to-date 10.582
# 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.878
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.442
After features/support/hooks.rb:339 0.740
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
21.317
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.560
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.054
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.475
After features/support/hooks.rb:339 0.881
After features/support/hooks.rb:108 0.000