Project Number Date
test_Tails_ISO_make-cloner-findable-via-backup-keyword 6 26 Oct 2026, 02:49

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:42.318 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:13.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.097
When I start Tails from USB drive "old" with network unplugged 55.168
Then the boot device has safe access rights 2.305
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.272
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.291
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 49.771
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 23.816
And I take note of which tps features are available 6.746
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.033
After features/support/hooks.rb:339 0.639
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.946
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.814
Then Tails is running from USB drive "old" 0.212
And all tps features are active 8.167
When I write some files expected to persist 1.203
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.864
And I take note of which tps features are available 6.299
And I shutdown Tails and wait for the computer to power off 4.251
# 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.549
After features/support/hooks.rb:339 0.395
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.544
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.531
And I log in to a new session 13.867
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.782
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.892
Then the running Tails is installed on USB drive "to_upgrade" 18.958
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 0.896
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.797
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.205
Then all tps features from the old Tails version are active 1.063
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.229
And the expected persistent files created with the old Tails version are present in the filesystem 1.010
And all persistent directories from the old Tails version have safe access rights 1.934
After features/support/hooks.rb:339 0.871
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:40.037
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.509
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.033
And Tor is ready 12.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.334
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.623
Given I shutdown Tails and wait for the computer to power off 5.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.264
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.665
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
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.102
# 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.169
When the network is plugged 0.036
And Tor is ready 10.646
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.864
Given I shutdown Tails and wait for the computer to power off 4.147
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.248
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.682
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.038
And Tor is ready 10.648
Then the Upgrader considers the system as up-to-date 0.100
# 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 4.006
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.882
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
20.366
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.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.033
And Tor is ready 9.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.753
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.000