Project Number Date
test_Tails_ISO_make-cloner-findable-via-backup-keyword 1 21 Oct 2026, 13:56

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:27.977 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:8.662
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.158
When I start Tails from USB drive "old" with network unplugged 51.364
Then the boot device has safe access rights 2.274
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.407
After features/support/hooks.rb:108 0.015
Tags: @product
1:24.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 49.153
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 23.915
And I take note of which tps features are available 6.464
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 4.110
After features/support/hooks.rb:339 0.382
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.700
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.058
Then Tails is running from USB drive "old" 0.227
And all tps features are active 7.196
When I write some files expected to persist 1.042
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.210
And all persistent directories from the old Tails version have safe access rights 2.004
And I take note of which tps features are available 6.440
And I shutdown Tails and wait for the computer to power off 2.594
# 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.670
After features/support/hooks.rb:339 0.125
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.965
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.453
And I log in to a new session 11.641
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.301
Then the running Tails is installed on USB drive "to_upgrade" 18.345
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 2.060
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.825
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.576
And the expected persistent files created with the old Tails version are present in the filesystem 1.047
And all persistent directories from the old Tails version have safe access rights 1.806
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.476
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 21.483
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.026
And Tor is ready 12.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.755
Given I shutdown Tails and wait for the computer to power off 5.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.937
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.134
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
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.132
# 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.171
When the network is plugged 0.035
And Tor is ready 10.508
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.317
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.711
Given I shutdown Tails and wait for the computer to power off 3.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.837
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.154
And the file system changes introduced in version 6.3~testoverlayfs are present 0.296
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.164
When the network is plugged 0.031
And Tor is ready 10.239
Then the Upgrader considers the system as up-to-date 0.111
# 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.580
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
19.081
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.854
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 9.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.463
After features/support/hooks.rb:339 0.600
After features/support/hooks.rb:108 0.000