Project Number Date
test_Tails_ISO_devel 3712 27 Feb 2025, 12: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 19:35.649 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.163
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 28.505
When I start Tails from USB drive "old" with network unplugged 1:42.326
Then the boot device has safe access rights 2.990
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 3.726
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:29.033
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.426
And I take note of which tps features are available 1.457
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:330 0.285
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.687
Then Tails is running from USB drive "old" 0.318
And all tps features are active 1.992
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 2.841
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 4.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.514
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.075
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.391
And I log in to a new session 18.995
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.587
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.573
Then the running Tails is installed on USB drive "to_upgrade" 20.707
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 2.097
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.571
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.825
Then all tps features from the old Tails version are active 1.688
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.359
And the expected persistent files created with the old Tails version are present in the filesystem 1.616
And all persistent directories from the old Tails version have safe access rights 2.532
After features/support/hooks.rb:330 1.354
After features/support/hooks.rb:100 0.010
6:48.271
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 13.844
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.288
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.760
When the network is plugged 0.068
And Tor is ready 22.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.381
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.017
Given I shutdown Tails and wait for the computer to power off 13.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.529
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.388
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# 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.271
When the network is plugged 0.078
And Tor is ready 19.338
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.214
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.578
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.649
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.551
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.566
When the network is plugged 0.089
And Tor is ready 23.136
Then the Upgrader considers the system as up-to-date 0.320
# 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.663
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.188
After features/support/hooks.rb:330 0.833
After features/support/hooks.rb:100 0.022
41.736
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 11.784
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.135
And Tor is ready 22.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.720
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.000