Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 29 29 Mar 2025, 21: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 19:2.403 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:0.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.671
When I start Tails from USB drive "old" with network unplugged 1:25.083
Then the boot device has safe access rights 2.887
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.018
After features/support/hooks.rb:100 0.050
Tags: @product
2:7.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:23.716
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 32.515
And I take note of which tps features are available 1.412
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.311
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.179
Then Tails is running from USB drive "old" 1.041
And all tps features are active 1.937
When I write some files expected to persist 1.617
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 3.030
And I take note of which tps features are available 0.513
And I shutdown Tails and wait for the computer to power off 4.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.906
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.006
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 10.769
And I log in to a new session 19.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.479
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.198
Then the running Tails is installed on USB drive "to_upgrade" 28.432
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.159
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.117
Then all tps features from the old Tails version are active 1.578
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.987
And the expected persistent files created with the old Tails version are present in the filesystem 1.338
And all persistent directories from the old Tails version have safe access rights 2.315
After features/support/hooks.rb:330 1.557
After features/support/hooks.rb:100 0.009
6:28.657
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 10.964
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.075
And Tor is ready 22.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.247
Given I shutdown Tails and wait for the computer to power off 8.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.629
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.295
When the network is plugged 0.070
And Tor is ready 18.847
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.893
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.179
Given I shutdown Tails and wait for the computer to power off 4.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.345
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.861
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.273
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.075
And Tor is ready 19.948
Then the Upgrader considers the system as up-to-date 0.317
# 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 14.004
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.560
After features/support/hooks.rb:330 0.695
After features/support/hooks.rb:100 0.017
37.070
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 9.608
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.553
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.936
After features/support/hooks.rb:330 0.652
After features/support/hooks.rb:100 0.000