Project Number Date
test_Tails_ISO_stable 6509 17 Jul 2026, 11:35

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:32.992 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:6.644
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 12.957
When I start Tails from USB drive "old" with network unplugged 49.499
Then the boot device has safe access rights 2.470
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.448
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 51.675
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 23.469
And I take note of which tps features are available 3.571
Then a Tails persistence partition exists on USB drive "old" 0.505
And I shutdown Tails and wait for the computer to power off 7.994
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.878
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:2.796
Then Tails is running from USB drive "old" 0.250
And all tps features are active 4.878
When I write some files expected to persist 1.146
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 1.736
And I take note of which tps features are available 3.601
And I shutdown Tails and wait for the computer to power off 8.214
# 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" 11.706
After features/support/hooks.rb:339 0.416
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.572
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.017
And I log in to a new session 11.109
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.838
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.668
Then the running Tails is installed on USB drive "to_upgrade" 14.442
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 2.144
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.993
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:1.676
Then all tps features from the old Tails version are active 0.839
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.291
And the expected persistent files created with the old Tails version are present in the filesystem 0.967
And all persistent directories from the old Tails version have safe access rights 1.957
After features/support/hooks.rb:339 0.693
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.881
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 with a persistent partition enabled and logged in 7.972
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.016
And Tor is ready 12.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.848
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.295
Given I shutdown Tails and wait for the computer to power off 9.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.166
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.672
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.203
When the network is plugged 0.015
And Tor is ready 10.793
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.213
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.846
Given I shutdown Tails and wait for the computer to power off 4.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.168
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.632
And the file system changes introduced in version 6.3~testoverlayfs are present 0.284
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.016
And Tor is ready 10.828
Then the Upgrader considers the system as up-to-date 10.596
# 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.284
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 1.003
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.541
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 with a persistent partition enabled and logged in 7.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.366
After features/support/hooks.rb:339 0.660
After features/support/hooks.rb:108 0.000