Project Number Date
test_Tails_ISO_stable 6552 02 Aug 2026, 11:43

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:8.567 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
59.927
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.129
When I start Tails from USB drive "old" with network unplugged 43.124
Then the boot device has safe access rights 1.889
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.145
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.629
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.446
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 47.253
Then Tails is running from USB drive "old" 0.212
And I create a persistent partition 22.157
And I take note of which tps features are available 6.044
Then a Tails persistence partition exists on USB drive "old" 0.557
And I shutdown Tails and wait for the computer to power off 4.145
After features/support/hooks.rb:339 0.423
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.550
Then Tails is running from USB drive "old" 0.226
And all tps features are active 7.088
When I write some files expected to persist 0.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.102
And all persistence configuration files have safe access rights 0.243
And all persistent directories from the old Tails version have safe access rights 1.452
And I take note of which tps features are available 6.079
And I shutdown Tails and wait for the computer to power off 2.868
# 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.057
After features/support/hooks.rb:339 0.107
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.080
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.035
And I log in to a new session 9.862
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.611
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.373
Then the running Tails is installed on USB drive "to_upgrade" 17.770
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.899
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.378
Then all tps features from the old Tails version are active 1.002
And Tails is running from USB drive "to_upgrade" 0.179
And the boot device has safe access rights 1.835
And the expected persistent files created with the old Tails version are present in the filesystem 0.873
And all persistent directories from the old Tails version have safe access rights 1.429
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.441
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 21.254
And no SquashFS delta is installed 0.044
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.274
When the network is plugged 0.033
And Tor is ready 12.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.512
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.876
Given I shutdown Tails and wait for the computer to power off 5.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.970
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.960
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.132
When the network is plugged 0.031
And Tor is ready 10.248
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.922
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.499
Given I shutdown Tails and wait for the computer to power off 2.575
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.871
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 7.532
And the file system changes introduced in version 6.3~testoverlayfs are present 0.264
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.033
And Tor is ready 10.157
Then the Upgrader considers the system as up-to-date 0.097
# 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 3.204
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.275
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
31.192
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 20.901
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.862
After features/support/hooks.rb:339 0.914
After features/support/hooks.rb:108 0.000