Project Number Date
test_Tails_ISO_devel 3757 27 Mar 2025, 10:28

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 19:49.182 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:16.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 30.838
When I start Tails from USB drive "old" with network unplugged 1:40.502
Then the boot device has safe access rights 3.011
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 3.720
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.215
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:32.463
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 30.825
And I take note of which tps features are available 1.357
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.221
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.457
Then Tails is running from USB drive "old" 0.406
And all tps features are active 1.935
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.885
And I take note of which tps features are available 0.672
And I shutdown Tails and wait for the computer to power off 4.714
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.906
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.292
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.195
And I log in to a new session 24.437
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.271
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.781
Then the running Tails is installed on USB drive "to_upgrade" 25.706
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 2.095
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.558
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.227
And the expected persistent files created with the old Tails version are present in the filesystem 1.821
And all persistent directories from the old Tails version have safe access rights 2.745
After features/support/hooks.rb:330 1.679
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:44.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.793
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.068
And Tor is ready 22.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.041
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.684
Given I shutdown Tails and wait for the computer to power off 13.510
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.299
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.361
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.255
When the network is plugged 0.084
And Tor is ready 19.480
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.449
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.967
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.159
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.022
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.269
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.071
And Tor is ready 19.007
Then the Upgrader considers the system as up-to-date 0.292
# 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 14.988
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.915
After features/support/hooks.rb:330 0.739
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.849
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 21.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.045
After features/support/hooks.rb:330 0.667
After features/support/hooks.rb:100 0.000