Project Number Date
test_Tails_ISO_devel 4172 16 Jan 2026, 11:51

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 11:41.522 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:16.184
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.108
When I start Tails from USB drive "old" with network unplugged 57.406
Then the boot device has safe access rights 2.792
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.447
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 54.904
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.669
And I take note of which tps features are available 0.702
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 7.976
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.728
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.185
When I write some files expected to persist 1.515
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.869
And I take note of which tps features are available 0.213
And I shutdown Tails and wait for the computer to power off 8.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.519
After features/support/hooks.rb:331 0.492
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.302
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.492
And I log in to a new session 11.319
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.741
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.079
Then the running Tails is installed on USB drive "to_upgrade" 16.152
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 3.981
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.312
Then all tps features from the old Tails version are active 0.873
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.211
And all persistent directories from the old Tails version have safe access rights 2.280
After features/support/hooks.rb:331 0.857
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
3:43.861
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 9.161
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.015
And Tor is ready 13.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.985
Given I shutdown Tails and wait for the computer to power off 9.656
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.551
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.103
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.205
When the network is plugged 0.015
And Tor is ready 11.375
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.804
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.360
Given I shutdown Tails and wait for the computer to power off 8.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.180
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.018
And Tor is ready 10.262
Then the Upgrader considers the system as up-to-date 10.592
# 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.815
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
19.784
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 7.997
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.016
And Tor is ready 10.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.346
After features/support/hooks.rb:331 0.962
After features/support/hooks.rb:100 0.000