Project Number Date
test_Tails_ISO_stable 5986 06 Dec 2025, 11:37

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 15:42.601 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:4.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.120
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 33.034
When I start Tails from USB drive "old" with network unplugged 1:26.025
Then the boot device has safe access rights 3.108
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:331 4.021
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:24.675
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 30.714
And I take note of which tps features are available 1.476
Then a Tails persistence partition exists on USB drive "old" 0.982
And I shutdown Tails and wait for the computer to power off 8.012
After features/support/hooks.rb:331 0.643
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.358
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 5.272
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.428
Then Tails is running from USB drive "old" 0.779
And all tps features are active 2.172
When I write some files expected to persist 1.693
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.370
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 7.577
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.012
After features/support/hooks.rb:331 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.713
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 10.443
And I log in to a new session 9.765
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.325
And I plug USB drive "to_upgrade" 2.104
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.649
Then the running Tails is installed on USB drive "to_upgrade" 20.008
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 3.810
After features/support/hooks.rb:100 0.000
Tags: @product
1:30.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.596
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.947
And all persistent directories from the old Tails version have safe access rights 3.287
After features/support/hooks.rb:331 0.930
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:37.700
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 10.468
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.082
And Tor is ready 13.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.662
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.472
Given I shutdown Tails and wait for the computer to power off 8.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.878
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.574
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.188
# 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.279
When the network is plugged 0.054
And Tor is ready 12.573
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.049
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.777
Given I shutdown Tails and wait for the computer to power off 8.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.081
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 14.571
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 5.011
And Tor is ready 10.541
Then the Upgrader considers the system as up-to-date 0.154
# 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 7.818
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.575
After features/support/hooks.rb:331 1.175
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
23.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.972
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 11.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.607
After features/support/hooks.rb:331 1.002
After features/support/hooks.rb:100 0.000