Project Number Date
test_Tails_ISO_devel 4592 03 Sep 2026, 17:50

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 12:17.845 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:14.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.754
When I start Tails from USB drive "old" with network unplugged 56.976
Then the boot device has safe access rights 2.363
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.172
After features/support/hooks.rb:108 0.008
Tags: @product
1:26.497
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 51.531
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.858
And I take note of which tps features are available 6.311
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 3.882
After features/support/hooks.rb:339 0.341
After features/support/hooks.rb:108 0.006
Tags: @product
1:43.233
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.503
Then Tails is running from USB drive "old" 0.234
And all tps features are active 7.256
When I write some files expected to persist 1.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.117
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 2.062
And I take note of which tps features are available 9.088
And I shutdown Tails and wait for the computer to power off 2.916
# 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" 14.531
After features/support/hooks.rb:339 0.605
After features/support/hooks.rb:108 0.006
Tags: @product
2:21.449
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 10.329
And I log in to a new session 14.177
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.128
Then the running Tails is installed on USB drive "to_upgrade" 19.595
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 2.590
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.351
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.419
Then all tps features from the old Tails version are active 1.268
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 3.077
And the expected persistent files created with the old Tails version are present in the filesystem 1.262
And all persistent directories from the old Tails version have safe access rights 1.991
After features/support/hooks.rb:339 0.853
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
3:58.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.075
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.034
And Tor is ready 13.302
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.167
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.890
Given I shutdown Tails and wait for the computer to power off 8.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.906
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.843
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# 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.275
When the network is plugged 0.055
And Tor is ready 9.743
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.378
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.927
Given I shutdown Tails and wait for the computer to power off 4.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.127
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.600
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.225
When the network is plugged 0.025
And Tor is ready 10.661
Then the Upgrader considers the system as up-to-date 10.437
# 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.735
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.329
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.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.489
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.000