Project Number Date
test_Tails_ISO_devel 4075 15 Nov 2025, 13:34

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 17:9.602 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
2:7.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 34.061
When I start Tails from USB drive "old" with network unplugged 1:28.131
Then the boot device has safe access rights 3.400
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.608
After features/support/hooks.rb:100 0.031
Tags: @product
2:10.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login 1:26.743
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 33.777
And I take note of which tps features are available 1.134
Then a Tails persistence partition exists on USB drive "old" 0.634
And I shutdown Tails and wait for the computer to power off 7.881
After features/support/hooks.rb:331 0.375
After features/support/hooks.rb:100 0.012
Tags: @product
2:43.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.596
Then Tails is running from USB drive "old" 0.715
And all tps features are active 1.806
When I write some files expected to persist 1.398
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 2.136
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 8.097
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.908
After features/support/hooks.rb:331 0.146
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.496
And I log in to a new session 11.017
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.574
And I plug USB drive "to_upgrade" 2.857
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.114
Then the running Tails is installed on USB drive "to_upgrade" 19.383
And I unplug USB drive "to_upgrade" 0.170
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:331 3.727
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.502
Then all tps features from the old Tails version are active 3.844
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 4.091
And the expected persistent files created with the old Tails version are present in the filesystem 1.341
And all persistent directories from the old Tails version have safe access rights 3.110
After features/support/hooks.rb:331 1.053
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:27.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.959
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
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.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.062
And Tor is ready 43.568
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.715
Given I shutdown Tails and wait for the computer to power off 9.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.202
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
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.148
# 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.238
When the network is plugged 0.085
And Tor is ready 12.505
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.805
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.523
Given I shutdown Tails and wait for the computer to power off 8.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.577
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.325
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.055
And Tor is ready 13.138
Then the Upgrader considers the system as up-to-date 0.184
# 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 6.092
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.456
After features/support/hooks.rb:331 0.978
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
22.624
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.698
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 9.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
After features/support/hooks.rb:331 0.812
After features/support/hooks.rb:100 0.000