Project Number Date
test_Tails_ISO_test-suite-options 2 17 Jun 2025, 23:09

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 22:55.685 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:31.758
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.120
And I plug USB drive "old" 1.102
And I write an old version of the Tails USB image to disk "old" 40.659
When I start Tails from USB drive "old" with network unplugged 1:45.015
Then the boot device has safe access rights 3.529
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.266
After features/support/hooks.rb:330 6.555
After features/support/hooks.rb:100 0.014
Tags: @product
2:33.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.414
And I start Tails from USB drive "old" with network unplugged and I login 1:43.517
Then Tails is running from USB drive "old" 0.512
And I create a persistent partition 37.077
And I take note of which tps features are available 2.640
Then a Tails persistence partition exists on USB drive "old" 0.755
And I shutdown Tails and wait for the computer to power off 8.872
After features/support/hooks.rb:330 2.426
After features/support/hooks.rb:100 0.088
Tags: @product
3:28.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.391
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:42.371
Then Tails is running from USB drive "old" 0.528
And all tps features are active 2.483
When I write some files expected to persist 2.063
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.678
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.633
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 32.504
After features/support/hooks.rb:330 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.684
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.290
And I log in to a new session 22.980
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.788
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.960
Then the running Tails is installed on USB drive "to_upgrade" 34.566
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.390
After features/support/hooks.rb:330 2.081
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:33.177
Then all tps features from the old Tails version are active 2.435
And Tails is running from USB drive "to_upgrade" 0.490
And the boot device has safe access rights 3.794
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 2.836
After features/support/hooks.rb:330 1.885
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:54.231
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 18.057
And no SquashFS delta is installed 0.485
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.719
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.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.078
And Tor is ready 27.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.771
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.410
Given I shutdown Tails and wait for the computer to power off 11.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.139
Then Tails is running version 6.2~testoverlayfs 0.461
And all tps features are active 3.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.510
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.303
When the network is plugged 0.079
And Tor is ready 23.526
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.951
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.916
Given I shutdown Tails and wait for the computer to power off 6.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.382
Then Tails is running version 6.3~testoverlayfs 0.029
And all tps features are active 2.990
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.408
When the network is plugged 0.105
And Tor is ready 22.871
Then the Upgrader considers the system as up-to-date 0.324
# 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 17.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.418
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
44.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.579
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.135
And Tor is ready 21.002
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.709
After features/support/hooks.rb:330 1.411
After features/support/hooks.rb:100 0.000