Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 18 18 Mar 2025, 21:55

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 18:34.500 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:4.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.133
When I start Tails from USB drive "old" with network unplugged 1:27.913
Then the boot device has safe access rights 3.217
And Tails is running from USB drive "old" 0.477
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.519
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.647
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:23.565
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 32.090
And I take note of which tps features are available 1.336
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.300
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.579
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.231
Then Tails is running from USB drive "old" 1.210
And all tps features are active 1.873
When I write some files expected to persist 2.335
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.410
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 6.193
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.055
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.593
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 10.758
And I log in to a new session 20.438
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.950
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.061
Then the running Tails is installed on USB drive "to_upgrade" 23.545
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 1.898
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.637
Then all tps features from the old Tails version are active 1.678
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.077
And the expected persistent files created with the old Tails version are present in the filesystem 1.591
And all persistent directories from the old Tails version have safe access rights 2.313
After features/support/hooks.rb:330 1.365
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:4.332
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.921
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.082
And Tor is ready 23.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.700
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.064
Given I shutdown Tails and wait for the computer to power off 8.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.806
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.924
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.302
When the network is plugged 0.065
And Tor is ready 16.251
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.416
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.195
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.469
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.430
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.394
When the network is plugged 0.107
And Tor is ready 20.918
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 14.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.106
After features/support/hooks.rb:330 0.738
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.792
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.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.848
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 20.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.945
After features/support/hooks.rb:330 1.286
After features/support/hooks.rb:100 0.000