Project Number Date
test_Tails_ISO_drop-net-dns-warning 1 22 May 2026, 18:17

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:59.785 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:12.867
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.397
When I start Tails from USB drive "old" with network unplugged 52.905
Then the boot device has safe access rights 3.482
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:335 3.804
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.421
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 57.372
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 25.649
And I take note of which tps features are available 0.365
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 8.171
After features/support/hooks.rb:335 0.442
After features/support/hooks.rb:104 0.009
Tags: @product
1:33.306
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.794
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.309
When I write some files expected to persist 1.312
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 1.922
And I take note of which tps features are available 0.177
And I shutdown Tails and wait for the computer to power off 8.430
# 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.532
After features/support/hooks.rb:335 0.555
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.508
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.844
And I log in to a new session 14.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.156
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.761
Then the running Tails is installed on USB drive "to_upgrade" 17.111
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:335 2.191
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.177
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.118
Then all tps features from the old Tails version are active 1.277
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 2.767
And the expected persistent files created with the old Tails version are present in the filesystem 1.339
And all persistent directories from the old Tails version have safe access rights 2.255
After features/support/hooks.rb:335 0.633
After features/support/hooks.rb:104 0.008
3:48.001
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.158
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.620
When the network is plugged 0.026
And Tor is ready 12.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.265
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.316
Given I shutdown Tails and wait for the computer to power off 9.794
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.152
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.210
When the network is plugged 0.017
And Tor is ready 11.735
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.608
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.746
Given I shutdown Tails and wait for the computer to power off 7.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.402
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.020
And Tor is ready 11.271
Then the Upgrader considers the system as up-to-date 10.589
# 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.413
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:335 0.954
After features/support/hooks.rb:104 0.022
21.502
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.346
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
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.078
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.794
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.971
After features/support/hooks.rb:335 0.783
After features/support/hooks.rb:104 0.000