Project Number Date
test_Tails_ISO_test-suite-options 14 30 Jun 2025, 21:12

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 27:42.066 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:41.527
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 40.037
When I start Tails from USB drive "old" with network unplugged 1:54.459
Then the boot device has safe access rights 4.687
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 7.131
After features/support/hooks.rb:100 0.013
Tags: @product
3:0.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 2:0.444
Then Tails is running from USB drive "old" 2.863
And I create a persistent partition 44.279
And I take note of which tps features are available 2.945
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.831
After features/support/hooks.rb:330 2.458
After features/support/hooks.rb:100 0.027
Tags: @product
4:30.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.734
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:29.989
Then Tails is running from USB drive "old" 0.581
And all tps features are active 2.473
When I write some files expected to persist 2.070
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.634
And all persistent directories from the old Tails version have safe access rights 7.406
And I take note of which tps features are available 0.897
And I shutdown Tails and wait for the computer to power off 6.961
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.915
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.008
Tags: @product
3:24.431
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 without a persistent partition and stopped at Tails Greeter's login screen 13.648
And I log in to a new session 28.585
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.753
And I plug USB drive "to_upgrade" 4.779
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.704
Then the running Tails is installed on USB drive "to_upgrade" 43.276
And I unplug USB drive "to_upgrade" 0.391
And I unplug USB drive "__internal" 0.292
After features/support/hooks.rb:330 4.895
After features/support/hooks.rb:100 0.000
Tags: @product
3:13.398
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.459
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:55.716
Then all tps features from the old Tails version are active 6.350
And Tails is running from USB drive "to_upgrade" 1.497
And the boot device has safe access rights 4.909
And the expected persistent files created with the old Tails version are present in the filesystem 1.571
And all persistent directories from the old Tails version have safe access rights 2.893
After features/support/hooks.rb:330 1.958
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:37.042
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 17.831
And no SquashFS delta is installed 0.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.744
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.572
When the network is plugged 0.078
And Tor is ready 36.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.823
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.258
Given I shutdown Tails and wait for the computer to power off 11.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:0.984
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 6.670
And the file system changes introduced in version 6.2~testoverlayfs are present 0.670
And only the 6.2~testoverlayfs SquashFS delta is installed 0.203
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.574
# 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.601
When the network is plugged 0.110
And Tor is ready 22.555
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 15.445
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.691
Given I shutdown Tails and wait for the computer to power off 10.040
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:42.810
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.418
And the file system changes introduced in version 6.3~testoverlayfs are present 0.602
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.415
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.352
When the network is plugged 0.083
And Tor is ready 37.816
Then the Upgrader considers the system as up-to-date 0.312
# 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.882
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.758
After features/support/hooks.rb:330 0.966
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
1:14.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the signing key used by the Upgrader is outdated 0.152
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 56.917
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.001
After features/support/hooks.rb:330 0.980
After features/support/hooks.rb:100 0.000