Project Number Date
test_Tails_ISO_devel 3793 29 Apr 2025, 13:20

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 20:21.436 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:7.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.725
When I start Tails from USB drive "old" with network unplugged 1:32.442
Then the boot device has safe access rights 3.118
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.759
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:32.190
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 31.019
And I take note of which tps features are available 2.469
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.596
After features/support/hooks.rb:330 0.214
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.353
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.215
When I write some files expected to persist 2.012
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.656
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 6.574
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.190
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.908
And I log in to a new session 20.912
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.916
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.599
Then the running Tails is installed on USB drive "to_upgrade" 26.540
And I unplug USB drive "to_upgrade" 0.376
And I unplug USB drive "__internal" 0.243
After features/support/hooks.rb:330 1.300
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.388
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.638
Then all tps features from the old Tails version are active 1.773
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.789
And the expected persistent files created with the old Tails version are present in the filesystem 1.504
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:330 1.274
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:14.140
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.647
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.091
And Tor is ready 24.256
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.977
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.108
Given I shutdown Tails and wait for the computer to power off 9.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.772
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.350
And the file system changes introduced in version 6.2~testoverlayfs are present 0.434
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.397
# 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.359
When the network is plugged 0.087
And Tor is ready 17.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.485
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.155
Given I shutdown Tails and wait for the computer to power off 4.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.583
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.292
And Tor is ready 18.726
Then the Upgrader considers the system as up-to-date 0.305
# 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 15.336
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.709
After features/support/hooks.rb:330 0.855
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
36.500
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 9.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 19.233
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.936
After features/support/hooks.rb:330 1.718
After features/support/hooks.rb:100 0.000