Project Number Date
test_Tails_ISO_stable 5644 13 May 2025, 12:40

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:36.357 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:10.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.299
When I start Tails from USB drive "old" with network unplugged 1:33.037
Then the boot device has safe access rights 3.180
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 3.718
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:28.885
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 32.173
And I take note of which tps features are available 1.809
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.609
After features/support/hooks.rb:330 0.226
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.971
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 "old" with network unplugged and I login with persistence enabled 2:23.459
Then Tails is running from USB drive "old" 0.382
And all tps features are active 1.898
When I write some files expected to persist 1.881
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.554
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.472
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.034
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.967
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 without a persistent partition and stopped at Tails Greeter's login screen 10.332
And I log in to a new session 18.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.953
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.947
Then the running Tails is installed on USB drive "to_upgrade" 22.237
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 3.734
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.935
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.224
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.516
And the expected persistent files created with the old Tails version are present in the filesystem 1.449
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:330 1.313
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:51.823
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 11.130
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.077
And Tor is ready 18.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.876
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.906
Given I shutdown Tails and wait for the computer to power off 8.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.426
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 1.968
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.290
When the network is plugged 0.056
And Tor is ready 17.574
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.500
Given I shutdown Tails and wait for the computer to power off 6.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.264
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.319
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.100
And Tor is ready 19.181
Then the Upgrader considers the system as up-to-date 11.123
# 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 16.437
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.568
After features/support/hooks.rb:330 0.694
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.022
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 10.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 18.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.567
After features/support/hooks.rb:330 0.891
After features/support/hooks.rb:100 0.000