Project Number Date
test_Tails_ISO_21618-remove-tcpdump 1 26 May 2026, 14:28

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:48.496 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:13.984
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.971
When I start Tails from USB drive "old" with network unplugged 55.255
Then the boot device has safe access rights 2.860
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:335 1.655
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.579
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 58.377
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 23.747
And I take note of which tps features are available 0.455
Then a Tails persistence partition exists on USB drive "old" 0.596
And I shutdown Tails and wait for the computer to power off 8.015
After features/support/hooks.rb:335 0.386
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.982
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.778
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.176
When I write some files expected to persist 1.366
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.066
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 8.110
# 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" 12.460
After features/support/hooks.rb:335 0.386
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.013
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.346
And I log in to a new session 12.834
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.809
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.897
Then the running Tails is installed on USB drive "to_upgrade" 16.549
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:335 2.579
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.559
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.421
Then all tps features from the old Tails version are active 0.992
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.700
And the expected persistent files created with the old Tails version are present in the filesystem 1.091
And all persistent directories from the old Tails version have safe access rights 1.985
After features/support/hooks.rb:335 0.732
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:48.375
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.292
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.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.015
And Tor is ready 12.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.819
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.673
Given I shutdown Tails and wait for the computer to power off 9.513
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.526
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.539
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.200
# 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.289
When the network is plugged 0.035
And Tor is ready 10.234
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.150
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.670
Given I shutdown Tails and wait for the computer to power off 8.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.246
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.174
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.019
And Tor is ready 11.378
Then the Upgrader considers the system as up-to-date 10.531
# 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 4.800
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.491
After features/support/hooks.rb:335 1.055
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.999
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.705
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.284
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.661
After features/support/hooks.rb:335 0.856
After features/support/hooks.rb:104 0.000