Project Number Date
test_Tails_ISO_21916-debian-packages 2 16 Nov 2026, 20:55

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:44.533 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:17.409
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.932
When I start Tails from USB drive "old" with network unplugged 59.353
Then the boot device has safe access rights 2.392
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.458
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.060
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 50.260
Then Tails is running from USB drive "old" 0.269
And I create a persistent partition 24.503
And I take note of which tps features are available 7.273
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 4.115
After features/support/hooks.rb:339 0.379
After features/support/hooks.rb:108 0.008
Tags: @product
1:40.713
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.014
Then Tails is running from USB drive "old" 0.253
And all tps features are active 9.371
When I write some files expected to persist 1.151
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 1.837
And I take note of which tps features are available 7.159
And I shutdown Tails and wait for the computer to power off 4.167
# 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.940
After features/support/hooks.rb:339 0.115
After features/support/hooks.rb:108 0.009
Tags: @product
2:15.643
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 without a persistent partition and stopped at Tails Greeter's login screen 8.525
And I log in to a new session 13.366
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.292
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.281
Then the running Tails is installed on USB drive "to_upgrade" 18.636
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.820
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.771
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.204
Then all tps features from the old Tails version are active 1.136
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.285
And the expected persistent files created with the old Tails version are present in the filesystem 1.050
And all persistent directories from the old Tails version have safe access rights 1.795
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.018
3:34.747
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.080
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.056
And Tor is ready 11.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.065
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.501
Given I shutdown Tails and wait for the computer to power off 7.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.166
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.773
And the file system changes introduced in version 6.2~testoverlayfs are present 0.187
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.196
When the network is plugged 0.023
And Tor is ready 10.807
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.307
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.687
Given I shutdown Tails and wait for the computer to power off 4.081
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.591
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.516
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.094
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.034
And Tor is ready 10.502
Then the Upgrader considers the system as up-to-date 0.176
# 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.685
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:339 0.643
After features/support/hooks.rb:108 0.033
19.189
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.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.080
After features/support/hooks.rb:339 0.986
After features/support/hooks.rb:108 0.000