Project Number Date
test_Tails_ISO_devel 4659 06 Oct 2026, 07:45

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:4.854 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:0.681
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.295
When I start Tails from USB drive "old" with network unplugged 43.473
Then the boot device has safe access rights 2.150
And Tails is running from USB drive "old" 0.207
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.333
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 47.245
Then Tails is running from USB drive "old" 0.179
And I create a persistent partition 23.532
And I take note of which tps features are available 6.627
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 4.102
After features/support/hooks.rb:339 0.566
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.276
Then Tails is running from USB drive "old" 0.237
And all tps features are active 7.446
When I write some files expected to persist 1.303
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.630
And I take note of which tps features are available 6.033
And I shutdown Tails and wait for the computer to power off 2.507
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.638
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.100
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.237
And I log in to a new session 13.188
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.184
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.634
Then the running Tails is installed on USB drive "to_upgrade" 17.791
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.772
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.457
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.292
Then all tps features from the old Tails version are active 1.248
And Tails is running from USB drive "to_upgrade" 0.156
And the boot device has safe access rights 2.192
And the expected persistent files created with the old Tails version are present in the filesystem 0.910
And all persistent directories from the old Tails version have safe access rights 1.575
After features/support/hooks.rb:339 0.721
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:30.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.281
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.150
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.024
And Tor is ready 13.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.297
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.843
Given I shutdown Tails and wait for the computer to power off 5.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.571
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.728
And the file system changes introduced in version 6.2~testoverlayfs are present 0.166
And only the 6.2~testoverlayfs SquashFS delta is installed 0.031
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.197
When the network is plugged 0.025
And Tor is ready 10.176
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.920
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.760
Given I shutdown Tails and wait for the computer to power off 3.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.762
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.275
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.030
And Tor is ready 10.347
Then the Upgrader considers the system as up-to-date 0.088
# 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.422
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:339 0.971
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
18.335
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.021
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.041
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.872
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.000