Project Number Date
test_Tails_ISO_stable 5486 03 Mar 2025, 13:00

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 21:31.800 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.728
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.979
When I start Tails from USB drive "old" with network unplugged 1:38.953
Then the boot device has safe access rights 3.298
And Tails is running from USB drive "old" 0.431
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 3.579
After features/support/hooks.rb:100 0.026
Tags: @product
2:7.682
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:25.373
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 30.806
And I take note of which tps features are available 1.804
Then a Tails persistence partition exists on USB drive "old" 0.802
And I shutdown Tails and wait for the computer to power off 8.276
After features/support/hooks.rb:330 0.284
After features/support/hooks.rb:100 0.008
Tags: @product
3:13.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.410
Then Tails is running from USB drive "old" 0.652
And all tps features are active 2.793
When I write some files expected to persist 5.266
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 3.712
And I take note of which tps features are available 0.572
And I shutdown Tails and wait for the computer to power off 6.577
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.367
After features/support/hooks.rb:330 0.507
After features/support/hooks.rb:100 0.025
Tags: @product
2:50.057
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.757
And I log in to a new session 21.406
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.952
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.211
Then the running Tails is installed on USB drive "to_upgrade" 23.604
And I unplug USB drive "to_upgrade" 0.282
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:330 2.659
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.389
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.288
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.275
Then all tps features from the old Tails version are active 3.479
And Tails is running from USB drive "to_upgrade" 0.482
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.590
And all persistent directories from the old Tails version have safe access rights 2.765
After features/support/hooks.rb:330 1.334
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:59.265
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 24.265
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.528
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.672
When the network is plugged 0.104
And Tor is ready 27.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.404
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.746
Given I shutdown Tails and wait for the computer to power off 11.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.204
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 3.593
And the file system changes introduced in version 6.2~testoverlayfs are present 0.382
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.513
# 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.379
When the network is plugged 0.104
And Tor is ready 21.276
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.205
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.380
Given I shutdown Tails and wait for the computer to power off 6.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.312
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.385
And the file system changes introduced in version 6.3~testoverlayfs are present 0.671
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.103
And Tor is ready 20.656
Then the Upgrader considers the system as up-to-date 0.344
# 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.628
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.120
After features/support/hooks.rb:330 1.026
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
38.403
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.873
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.170
And Tor is ready 18.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.123
After features/support/hooks.rb:330 1.332
After features/support/hooks.rb:100 0.000