Project Number Date
test_Tails_ISO_21901-refresh-about-tor-7-17 1 05 Nov 2026, 21:12

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:20.058 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:11.477
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.703
When I start Tails from USB drive "old" with network unplugged 53.657
Then the boot device has safe access rights 2.357
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.631
After features/support/hooks.rb:108 0.033
Tags: @product
1:23.901
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.018
Then Tails is running from USB drive "old" 0.173
And I create a persistent partition 23.224
And I take note of which tps features are available 6.726
Then a Tails persistence partition exists on USB drive "old" 0.501
And I shutdown Tails and wait for the computer to power off 5.173
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.138
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.504
Then Tails is running from USB drive "old" 0.192
And all tps features are active 6.931
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.297
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 6.141
And I shutdown Tails and wait for the computer to power off 3.983
# 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.546
After features/support/hooks.rb:339 0.214
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.999
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.564
And I log in to a new session 13.007
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.737
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.995
Then the running Tails is installed on USB drive "to_upgrade" 18.256
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.834
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.832
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.275
And the expected persistent files created with the old Tails version are present in the filesystem 0.852
And all persistent directories from the old Tails version have safe access rights 1.621
After features/support/hooks.rb:339 0.640
After features/support/hooks.rb:108 0.048
Tags: @product @automatic_upgrade
3:29.691
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.141
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.275
When the network is plugged 0.026
And Tor is ready 13.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.918
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.422
Given I shutdown Tails and wait for the computer to power off 5.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.213
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.208
When the network is plugged 0.029
And Tor is ready 10.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.328
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.749
Given I shutdown Tails and wait for the computer to power off 2.587
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.737
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.274
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.027
And Tor is ready 10.315
Then the Upgrader considers the system as up-to-date 0.150
# 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.421
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.928
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.854
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.109
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.041
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.534
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.846
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.000