Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 12 12 Mar 2025, 21:44

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:17.397 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:14.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.441
When I start Tails from USB drive "old" with network unplugged 1:33.003
Then the boot device has safe access rights 3.345
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.245
After features/support/hooks.rb:330 3.606
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.227
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 1:34.285
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 32.642
And I take note of which tps features are available 1.435
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.510
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.939
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.696
Then Tails is running from USB drive "old" 0.342
And all tps features are active 2.488
When I write some files expected to persist 1.790
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.431
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.482
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.138
And I log in to a new session 17.904
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.875
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.018
Then the running Tails is installed on USB drive "to_upgrade" 22.906
And I unplug USB drive "to_upgrade" 0.323
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:330 1.627
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.661
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.543
Then all tps features from the old Tails version are active 1.594
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.084
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.389
After features/support/hooks.rb:330 1.175
After features/support/hooks.rb:100 0.017
6:27.246
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 11.447
And no SquashFS delta is installed 0.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.407
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.066
And Tor is ready 18.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.654
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.550
Given I shutdown Tails and wait for the computer to power off 8.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.449
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.503
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.390
# 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.278
When the network is plugged 0.072
And Tor is ready 17.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.072
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.411
Given I shutdown Tails and wait for the computer to power off 4.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.801
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.858
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.065
And Tor is ready 20.317
Then the Upgrader considers the system as up-to-date 0.308
# 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.754
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.931
After features/support/hooks.rb:330 0.762
After features/support/hooks.rb:100 0.018
36.265
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 9.859
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.097
And Tor is ready 20.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.241
After features/support/hooks.rb:330 0.774
After features/support/hooks.rb:100 0.000