Project Number Date
test_Tails_ISO_stable 5749 29 Jun 2025, 12:46

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:48.936 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:5.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.931
When I start Tails from USB drive "old" with network unplugged 1:29.686
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 3.777
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:26.936
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 31.054
And I take note of which tps features are available 2.225
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.699
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.757
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.388
When I write some files expected to persist 1.625
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.387
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.185
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.514
After features/support/hooks.rb:330 0.098
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.067
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 9.950
And I log in to a new session 18.920
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.594
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.871
Then the running Tails is installed on USB drive "to_upgrade" 25.667
And I unplug USB drive "to_upgrade" 0.432
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 3.066
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.649
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.585
Then all tps features from the old Tails version are active 1.440
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.162
And the expected persistent files created with the old Tails version are present in the filesystem 1.340
And all persistent directories from the old Tails version have safe access rights 2.584
After features/support/hooks.rb:330 1.314
After features/support/hooks.rb:100 0.010
6:45.788
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.416
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.071
And Tor is ready 23.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.412
Given I shutdown Tails and wait for the computer to power off 9.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.342
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# 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.341
When the network is plugged 0.072
And Tor is ready 19.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.005
Given I shutdown Tails and wait for the computer to power off 4.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.147
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.810
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.125
# 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.516
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.076
And Tor is ready 17.742
Then the Upgrader considers the system as up-to-date 0.326
# 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.387
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.545
After features/support/hooks.rb:330 0.826
After features/support/hooks.rb:100 0.020
59.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 9.892
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 48.751
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.638
After features/support/hooks.rb:330 0.681
After features/support/hooks.rb:100 0.000