Project Number Date
test_Tails_ISO_post-7.15.1-release-process 3 24 Oct 2026, 19: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 11:26.249 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:20.349
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 13.418
When I start Tails from USB drive "old" with network unplugged 1:3.050
Then the boot device has safe access rights 1.990
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.717
After features/support/hooks.rb:108 0.012
Tags: @product
1:21.699
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 48.483
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.302
And I take note of which tps features are available 6.575
Then a Tails persistence partition exists on USB drive "old" 0.474
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.147
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.496
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.449
Then Tails is running from USB drive "old" 0.184
And all tps features are active 7.559
When I write some files expected to persist 1.060
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.504
And I take note of which tps features are available 5.848
And I shutdown Tails and wait for the computer to power off 2.549
# 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.813
After features/support/hooks.rb:339 0.325
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.137
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.387
And I log in to a new session 13.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.711
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.829
Then the running Tails is installed on USB drive "to_upgrade" 17.694
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 2.030
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.012
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.613
Then all tps features from the old Tails version are active 1.103
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.284
And the expected persistent files created with the old Tails version are present in the filesystem 0.976
And all persistent directories from the old Tails version have safe access rights 1.722
After features/support/hooks.rb:339 0.774
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:29.962
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.128
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.185
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.181
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.096
And Tor is ready 12.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.331
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.468
Given I shutdown Tails and wait for the computer to power off 5.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.476
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.175
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.167
When the network is plugged 0.031
And Tor is ready 10.344
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.876
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.619
Given I shutdown Tails and wait for the computer to power off 2.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.955
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.448
And the file system changes introduced in version 6.3~testoverlayfs are present 0.309
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.033
And Tor is ready 11.160
Then the Upgrader considers the system as up-to-date 0.105
# 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.671
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.889
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
18.591
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.945
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.560
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.000