Project Number Date
test_Tails_ISO_20979-pdfarranger 11 06 Jun 2025, 02:59

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:27.870 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:12.902
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.948
When I start Tails from USB drive "old" with network unplugged 1:37.649
Then the boot device has safe access rights 3.025
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.702
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.575
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:31.603
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 31.419
And I take note of which tps features are available 1.887
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 8.353
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.321
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.224
Then Tails is running from USB drive "old" 0.514
And all tps features are active 1.980
When I write some files expected to persist 2.384
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.396
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.525
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 6.441
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.828
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.305
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.291
And I log in to a new session 18.319
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.974
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.361
Then the running Tails is installed on USB drive "to_upgrade" 24.533
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:330 6.710
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.569
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.948
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.312
And the expected persistent files created with the old Tails version are present in the filesystem 1.742
And all persistent directories from the old Tails version have safe access rights 2.431
After features/support/hooks.rb:330 1.209
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
6:39.751
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 with a persistent partition enabled and logged in 11.453
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.060
And Tor is ready 21.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.162
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.575
Given I shutdown Tails and wait for the computer to power off 8.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.059
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.358
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.394
# 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.469
When the network is plugged 0.063
And Tor is ready 17.669
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.864
Given I shutdown Tails and wait for the computer to power off 6.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.267
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.323
When the network is plugged 0.064
And Tor is ready 18.121
Then the Upgrader considers the system as up-to-date 0.335
# 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.238
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.555
After features/support/hooks.rb:330 0.707
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.445
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 10.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.629
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 17.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.875
After features/support/hooks.rb:330 1.592
After features/support/hooks.rb:100 0.000