Project Number Date
test_Tails_ISO_21618-remove-tcpdump 2 26 May 2026, 16:52

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:57.872 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:25.510
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 14.515
When I start Tails from USB drive "old" with network unplugged 1:5.967
Then the boot device has safe access rights 3.198
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:335 3.585
After features/support/hooks.rb:104 0.022
Tags: @product
1:33.891
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 59.157
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 26.439
And I take note of which tps features are available 0.380
Then a Tails persistence partition exists on USB drive "old" 0.626
And I shutdown Tails and wait for the computer to power off 6.948
After features/support/hooks.rb:335 0.427
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.916
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.229
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.331
When I write some files expected to persist 1.361
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.334
And I take note of which tps features are available 0.177
And I shutdown Tails and wait for the computer to power off 4.072
# 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.542
After features/support/hooks.rb:335 0.469
After features/support/hooks.rb:104 0.006
Tags: @product
2:16.012
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 9.571
And I log in to a new session 13.699
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.090
And I plug USB drive "to_upgrade" 2.293
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.539
Then the running Tails is installed on USB drive "to_upgrade" 16.546
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.486
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.530
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.830
Then all tps features from the old Tails version are active 1.148
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.895
And the expected persistent files created with the old Tails version are present in the filesystem 1.204
And all persistent directories from the old Tails version have safe access rights 2.108
After features/support/hooks.rb:335 0.874
After features/support/hooks.rb:104 0.008
3:43.625
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.453
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.025
And Tor is ready 13.537
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.779
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.637
Given I shutdown Tails and wait for the computer to power off 9.772
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.208
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.189
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.186
# 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.215
When the network is plugged 0.025
And Tor is ready 11.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.710
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.886
Given I shutdown Tails and wait for the computer to power off 8.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.290
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.177
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.016
And Tor is ready 9.685
Then the Upgrader considers the system as up-to-date 10.569
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:335 0.843
After features/support/hooks.rb:104 0.011
20.384
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.998
After features/support/hooks.rb:335 0.843
After features/support/hooks.rb:104 0.000