Project Number Date
test_Tails_ISO_make-cloner-findable-via-backup-keyword 3 23 Oct 2026, 02:40

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:6.112 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:9.241
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.653
When I start Tails from USB drive "old" with network unplugged 52.019
Then the boot device has safe access rights 1.920
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.149
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.866
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.246
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.648
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 22.799
And I take note of which tps features are available 6.026
Then a Tails persistence partition exists on USB drive "old" 0.443
And I shutdown Tails and wait for the computer to power off 4.048
After features/support/hooks.rb:339 0.584
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.554
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 58.623
Then Tails is running from USB drive "old" 0.211
And all tps features are active 6.540
When I write some files expected to persist 0.891
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.253
And all persistent directories from the old Tails version have safe access rights 1.463
And I take note of which tps features are available 5.788
And I shutdown Tails and wait for the computer to power off 2.574
# 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.005
After features/support/hooks.rb:339 0.248
After features/support/hooks.rb:108 0.005
Tags: @product
2:24.867
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 21.640
And I log in to a new session 12.094
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.639
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.302
Then the running Tails is installed on USB drive "to_upgrade" 17.747
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.824
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.987
Then all tps features from the old Tails version are active 1.036
And Tails is running from USB drive "to_upgrade" 0.167
And the boot device has safe access rights 1.991
And the expected persistent files created with the old Tails version are present in the filesystem 0.888
And all persistent directories from the old Tails version have safe access rights 1.529
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.038
3:20.438
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 7.911
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.039
And Tor is ready 13.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.293
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.797
Given I shutdown Tails and wait for the computer to power off 5.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.484
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.154
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.089
# 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.186
When the network is plugged 0.023
And Tor is ready 10.002
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.942
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.481
Given I shutdown Tails and wait for the computer to power off 3.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.126
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.265
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.031
And Tor is ready 10.039
Then the Upgrader considers the system as up-to-date 0.102
# 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.055
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:339 0.909
After features/support/hooks.rb:108 0.019
19.083
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 7.569
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.033
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.270
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.891
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.000