Project Number Date
test_Tails_ISO_devel 3866 12 Jun 2025, 18:58

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 24:13.449 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:35.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 38.412
When I start Tails from USB drive "old" with network unplugged 1:50.607
Then the boot device has safe access rights 4.237
And Tails is running from USB drive "old" 0.430
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.390
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:330 3.956
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:43.377
Then Tails is running from USB drive "old" 0.457
And I create a persistent partition 36.594
And I take note of which tps features are available 3.087
Then a Tails persistence partition exists on USB drive "old" 1.127
And I shutdown Tails and wait for the computer to power off 10.135
After features/support/hooks.rb:330 0.282
After features/support/hooks.rb:100 0.014
Tags: @product
3:42.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.495
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:53.323
Then Tails is running from USB drive "old" 1.482
And all tps features are active 3.506
When I write some files expected to persist 2.162
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.387
And all persistence configuration files have safe access rights 0.505
And all persistent directories from the old Tails version have safe access rights 2.910
And I take note of which tps features are available 2.738
And I shutdown Tails and wait for the computer to power off 6.742
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.233
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.011
Tags: @product
3:19.121
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 21.917
And I log in to a new session 23.778
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.914
And I plug USB drive "to_upgrade" 3.319
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:59.277
Then the running Tails is installed on USB drive "to_upgrade" 27.922
And I unplug USB drive "to_upgrade" 0.507
And I unplug USB drive "__internal" 0.484
After features/support/hooks.rb:330 3.091
After features/support/hooks.rb:100 0.000
Tags: @product
3:0.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 1.822
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:45.203
Then all tps features from the old Tails version are active 2.804
And Tails is running from USB drive "to_upgrade" 0.557
And the boot device has safe access rights 4.871
And the expected persistent files created with the old Tails version are present in the filesystem 1.970
And all persistent directories from the old Tails version have safe access rights 2.876
After features/support/hooks.rb:330 1.296
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:12.545
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 41.448
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.614
When the network is plugged 0.094
And Tor is ready 25.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.468
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.613
Given I shutdown Tails and wait for the computer to power off 11.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:37.607
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.913
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# 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.312
When the network is plugged 0.084
And Tor is ready 22.570
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.295
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.627
Given I shutdown Tails and wait for the computer to power off 5.750
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.036
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.851
And the file system changes introduced in version 6.3~testoverlayfs are present 0.698
And only the 6.3~testoverlayfs SquashFS delta is installed 0.117
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.349
When the network is plugged 0.173
And Tor is ready 18.969
Then the Upgrader considers the system as up-to-date 0.360
# 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 19.503
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.953
After features/support/hooks.rb:330 1.269
After features/support/hooks.rb:100 0.057
Tags: @product @automatic_upgrade
48.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.541
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.099
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 22.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.626
After features/support/hooks.rb:330 1.095
After features/support/hooks.rb:100 0.000