Project Number Date
test_Tails_ISO_21916-debian-packages 1 16 Nov 2026, 20:23

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.401 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:20.088
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 19.163
When I start Tails from USB drive "old" with network unplugged 56.471
Then the boot device has safe access rights 2.409
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 4.233
After features/support/hooks.rb:108 0.018
Tags: @product
1:26.752
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login 49.951
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 24.648
And I take note of which tps features are available 6.957
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 4.207
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.458
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.427
Then Tails is running from USB drive "old" 0.312
And all tps features are active 9.451
When I write some files expected to persist 1.152
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 2.029
And I take note of which tps features are available 6.536
And I shutdown Tails and wait for the computer to power off 2.718
# 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.189
After features/support/hooks.rb:339 0.354
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.510
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.085
And I log in to a new session 11.887
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.330
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.769
Then the running Tails is installed on USB drive "to_upgrade" 18.346
And I unplug USB drive "to_upgrade" 0.353
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.645
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.140
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.733
Then all tps features from the old Tails version are active 1.035
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.222
And the expected persistent files created with the old Tails version are present in the filesystem 1.048
And all persistent directories from the old Tails version have safe access rights 1.796
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.020
3:37.914
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.555
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.027
And Tor is ready 13.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.247
Given I shutdown Tails and wait for the computer to power off 5.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.053
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.376
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.201
When the network is plugged 0.028
And Tor is ready 10.066
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.368
Given I shutdown Tails and wait for the computer to power off 3.943
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.943
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 9.549
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.031
And Tor is ready 11.482
Then the Upgrader considers the system as up-to-date 0.110
# 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.627
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.011
19.536
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 with a persistent partition enabled and logged in 8.177
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.930
After features/support/hooks.rb:339 0.602
After features/support/hooks.rb:108 0.000