Project Number Date
test_Tails_ISO_devel 4190 26 Jan 2026, 12:04

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:59.058 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:19.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.052
When I start Tails from USB drive "old" with network unplugged 1:0.735
Then the boot device has safe access rights 2.589
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 3.745
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 58.005
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.018
And I take note of which tps features are available 0.731
Then a Tails persistence partition exists on USB drive "old" 0.658
And I shutdown Tails and wait for the computer to power off 8.029
After features/support/hooks.rb:331 0.157
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.419
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.136
When I write some files expected to persist 1.291
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.140
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 4.191
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.673
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.006
Tags: @product
2:23.896
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 9.197
And I log in to a new session 13.562
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.000
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.645
Then the running Tails is installed on USB drive "to_upgrade" 17.944
And I unplug USB drive "to_upgrade" 0.168
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 1.562
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.363
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.106
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.253
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.785
And the expected persistent files created with the old Tails version are present in the filesystem 1.086
And all persistent directories from the old Tails version have safe access rights 1.690
After features/support/hooks.rb:331 0.916
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:48.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.488
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.016
And Tor is ready 13.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.178
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.637
Given I shutdown Tails and wait for the computer to power off 12.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.246
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.214
When the network is plugged 0.014
And Tor is ready 11.662
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.538
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.517
Given I shutdown Tails and wait for the computer to power off 8.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.000
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.850
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.017
And Tor is ready 11.983
Then the Upgrader considers the system as up-to-date 10.499
# 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.078
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:331 1.133
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
21.973
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.876
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.316
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.463
After features/support/hooks.rb:331 0.766
After features/support/hooks.rb:100 0.000