Project Number Date
test_Tails_ISO_21916-debian-packages 3 16 Nov 2026, 23:45

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:1.618 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:2.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.474
When I start Tails from USB drive "old" with network unplugged 45.213
Then the boot device has safe access rights 1.993
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.157
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.771
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.085
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 47.861
Then Tails is running from USB drive "old" 0.164
And I create a persistent partition 22.554
And I take note of which tps features are available 5.784
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 4.095
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.690
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.844
Then Tails is running from USB drive "old" 0.264
And all tps features are active 7.094
When I write some files expected to persist 0.833
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.214
And all persistent directories from the old Tails version have safe access rights 1.519
And I take note of which tps features are available 5.874
And I shutdown Tails and wait for the computer to power off 2.649
# 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.160
After features/support/hooks.rb:339 0.114
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.867
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 without a persistent partition and stopped at Tails Greeter's login screen 8.272
And I log in to a new session 13.796
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.775
Then the running Tails is installed on USB drive "to_upgrade" 16.954
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.104
After features/support/hooks.rb:339 2.174
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.919
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.495
Then all tps features from the old Tails version are active 0.946
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 1.909
And the expected persistent files created with the old Tails version are present in the filesystem 0.746
And all persistent directories from the old Tails version have safe access rights 1.541
After features/support/hooks.rb:339 0.782
After features/support/hooks.rb:108 0.005
3:34.429
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 20.938
And no SquashFS delta is installed 0.038
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.263
When the network is plugged 0.029
And Tor is ready 12.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.291
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.128
Given I shutdown Tails and wait for the computer to power off 5.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.384
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.284
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.162
When the network is plugged 0.026
And Tor is ready 10.102
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.896
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.579
Given I shutdown Tails and wait for the computer to power off 4.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.621
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.271
And the file system changes introduced in version 6.3~testoverlayfs are present 0.314
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.031
And Tor is ready 10.644
Then the Upgrader considers the system as up-to-date 0.081
# 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.070
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.301
After features/support/hooks.rb:339 0.935
After features/support/hooks.rb:108 0.018
19.263
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 7.600
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.080
After features/support/hooks.rb:339 0.877
After features/support/hooks.rb:108 0.000