Project Number Date
test_Tails_ISO_stable 6011 17 Dec 2025, 15:05

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 18:19.019 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:27.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.157
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 28.288
When I start Tails from USB drive "old" with network unplugged 53.618
Then the boot device has safe access rights 3.382
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 4.076
After features/support/hooks.rb:100 0.011
Tags: @product
1:50.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:7.180
Then Tails is running from USB drive "old" 0.863
And I create a persistent partition 31.615
And I take note of which tps features are available 1.228
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.342
After features/support/hooks.rb:331 0.404
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:25.637
Then Tails is running from USB drive "old" 0.302
And all tps features are active 2.007
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.890
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 10.728
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.307
After features/support/hooks.rb:331 0.622
After features/support/hooks.rb:100 0.010
Tags: @product
4:53.958
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 12.222
And I log in to a new session 16.460
And I clone USB drive "old" to a new USB drive "to_upgrade" 1:7.641
And I plug USB drive "to_upgrade" 2.689
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:45.908
Then the running Tails is installed on USB drive "to_upgrade" 23.080
And I unplug USB drive "to_upgrade" 0.836
And I unplug USB drive "__internal" 5.118
After features/support/hooks.rb:331 5.369
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.321
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 1.879
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.960
Then all tps features from the old Tails version are active 10.457
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.156
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 3.088
After features/support/hooks.rb:331 3.361
After features/support/hooks.rb:100 0.442
Tags: @product @automatic_upgrade
5:52.260
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.090
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.848
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 5.021
And Tor is ready 41.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.648
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.850
Given I shutdown Tails and wait for the computer to power off 7.903
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:31.153
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 12.587
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.204
# 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.321
When the network is plugged 0.069
And Tor is ready 12.878
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.586
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.986
Given I shutdown Tails and wait for the computer to power off 7.872
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.851
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.260
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.055
And Tor is ready 31.190
Then the Upgrader considers the system as up-to-date 0.141
# 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 5.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.501
After features/support/hooks.rb:331 0.821
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
22.946
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.414
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.110
And Tor is ready 10.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.006
After features/support/hooks.rb:331 2.118
After features/support/hooks.rb:100 0.000