Project Number Date
test_Tails_ISO_devel 3867 13 Jun 2025, 15:09

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 27:40.341 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
2:56.410
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 43.631
When I start Tails from USB drive "old" with network unplugged 2:1.312
Then the boot device has safe access rights 8.321
And Tails is running from USB drive "old" 0.818
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.144
And udev-watchdog is monitoring the correct device 0.390
And I unplug USB drive "old" 0.352
After features/support/hooks.rb:330 9.542
After features/support/hooks.rb:100 0.051
Tags: @product
2:59.412
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.075
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login 1:58.472
Then Tails is running from USB drive "old" 0.507
And I create a persistent partition 44.833
And I take note of which tps features are available 4.163
Then a Tails persistence partition exists on USB drive "old" 2.063
And I shutdown Tails and wait for the computer to power off 9.095
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.011
Tags: @product
4:8.362
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.853
Then Tails is running from USB drive "old" 4.440
And all tps features are active 4.135
When I write some files expected to persist 2.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.835
And I take note of which tps features are available 0.600
And I shutdown Tails and wait for the computer to power off 9.554
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 39.010
After features/support/hooks.rb:330 0.511
After features/support/hooks.rb:100 0.043
Tags: @product
3:24.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.066
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.811
And I log in to a new session 31.672
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.432
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.061
Then the running Tails is installed on USB drive "to_upgrade" 42.809
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.103
After features/support/hooks.rb:100 0.000
Tags: @product
3:22.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:6.312
Then all tps features from the old Tails version are active 5.975
And Tails is running from USB drive "to_upgrade" 0.937
And the boot device has safe access rights 4.845
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.905
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
9:57.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.513
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.553
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.538
When the network is plugged 0.090
And Tor is ready 31.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.393
Given I shutdown Tails and wait for the computer to power off 14.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:6.332
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 4.468
And the file system changes introduced in version 6.2~testoverlayfs are present 1.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.335
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.692
# 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.956
When the network is plugged 0.113
And Tor is ready 49.194
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.800
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.353
Given I shutdown Tails and wait for the computer to power off 6.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:58.302
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.963
And the file system changes introduced in version 6.3~testoverlayfs are present 2.087
And only the 6.3~testoverlayfs SquashFS delta is installed 0.225
# 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.826
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.079
When the network is plugged 0.189
And Tor is ready 24.087
Then the Upgrader considers the system as up-to-date 0.316
# 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 21.012
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.634
After features/support/hooks.rb:330 0.936
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
50.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 22.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.346
After features/support/hooks.rb:330 3.286
After features/support/hooks.rb:100 0.000