Project Number Date
test_Tails_ISO_devel 4136 24 Dec 2025, 11:09

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 10:25.051 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
55.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.175
When I start Tails from USB drive "old" with network unplugged 38.398
Then the boot device has safe access rights 2.466
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.914
After features/support/hooks.rb:100 0.005
Tags: @product
1:23.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 50.507
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 23.674
And I take note of which tps features are available 0.631
Then a Tails persistence partition exists on USB drive "old" 0.476
And I shutdown Tails and wait for the computer to power off 7.967
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.006
Tags: @product
1:18.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.549
Then Tails is running from USB drive "old" 0.210
And all tps features are active 1.102
When I write some files expected to persist 1.342
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.838
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 4.115
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.413
After features/support/hooks.rb:331 0.614
After features/support/hooks.rb:100 0.006
Tags: @product
2:7.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.896
And I log in to a new session 11.251
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.669
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.163
Then the running Tails is installed on USB drive "to_upgrade" 14.522
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 3.666
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.968
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.702
Then all tps features from the old Tails version are active 0.859
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.391
And the expected persistent files created with the old Tails version are present in the filesystem 1.051
And all persistent directories from the old Tails version have safe access rights 1.693
After features/support/hooks.rb:331 0.722
After features/support/hooks.rb:100 0.006
3:16.660
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.167
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.319
When the network is plugged 0.017
And Tor is ready 12.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.908
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.616
Given I shutdown Tails and wait for the computer to power off 9.212
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.705
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.060
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.194
When the network is plugged 0.016
And Tor is ready 9.695
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.759
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.632
Given I shutdown Tails and wait for the computer to power off 7.797
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 56.777
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.156
When the network is plugged 0.018
And Tor is ready 10.905
Then the Upgrader considers the system as up-to-date 0.098
# 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.772
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:331 0.736
After features/support/hooks.rb:100 0.021
17.937
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 7.318
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.998
After features/support/hooks.rb:331 0.768
After features/support/hooks.rb:100 0.000