Project Number Date
test_Tails_ISO_devel 3853 03 Jun 2025, 20:16

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 22:28.832 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:42.074
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.289
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 45.604
When I start Tails from USB drive "old" with network unplugged 1:49.894
Then the boot device has safe access rights 3.866
And Tails is running from USB drive "old" 0.430
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.269
After features/support/hooks.rb:330 3.811
After features/support/hooks.rb:100 0.013
Tags: @product
2:22.087
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:34.772
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 34.974
And I take note of which tps features are available 2.170
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.760
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.334
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.877
Then Tails is running from USB drive "old" 0.517
And all tps features are active 3.230
When I write some files expected to persist 2.173
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.473
And all persistent directories from the old Tails version have safe access rights 3.091
And I take note of which tps features are available 1.089
And I shutdown Tails and wait for the computer to power off 6.705
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.775
After features/support/hooks.rb:330 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.687
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 without a persistent partition and stopped at Tails Greeter's login screen 23.203
And I log in to a new session 20.193
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.784
And I plug USB drive "to_upgrade" 2.657
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.649
Then the running Tails is installed on USB drive "to_upgrade" 29.621
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.313
After features/support/hooks.rb:330 2.486
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.378
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.872
Then all tps features from the old Tails version are active 2.101
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.807
And the expected persistent files created with the old Tails version are present in the filesystem 2.193
And all persistent directories from the old Tails version have safe access rights 2.968
After features/support/hooks.rb:330 1.548
After features/support/hooks.rb:100 0.009
7:53.651
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 31.848
And no SquashFS delta is installed 0.319
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.431
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.569
When the network is plugged 0.234
And Tor is ready 19.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.663
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.885
Given I shutdown Tails and wait for the computer to power off 11.754
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.614
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.382
When the network is plugged 0.105
And Tor is ready 19.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.698
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.740
Given I shutdown Tails and wait for the computer to power off 6.905
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.931
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.488
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.098
And Tor is ready 47.123
Then the Upgrader considers the system as up-to-date 0.351
# 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 17.124
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.617
After features/support/hooks.rb:330 0.860
After features/support/hooks.rb:100 0.019
43.117
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 14.445
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.665
And Tor is ready 19.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.530
After features/support/hooks.rb:330 3.355
After features/support/hooks.rb:100 0.000