Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 6 07 Mar 2025, 00:23

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 20:33.949 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:17.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.010
When I start Tails from USB drive "old" with network unplugged 1:40.204
Then the boot device has safe access rights 3.182
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.661
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.073
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.283
And I start Tails from USB drive "old" with network unplugged and I login 1:31.562
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 32.705
And I take note of which tps features are available 2.342
Then a Tails persistence partition exists on USB drive "old" 0.904
And I shutdown Tails and wait for the computer to power off 8.910
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.012
Tags: @product
3:9.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.934
Then Tails is running from USB drive "old" 1.108
And all tps features are active 2.661
When I write some files expected to persist 3.553
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.652
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 3.259
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 6.703
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.842
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.951
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 25.152
And I log in to a new session 22.361
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.823
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.990
Then the running Tails is installed on USB drive "to_upgrade" 23.620
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:330 2.847
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.691
Then all tps features from the old Tails version are active 1.726
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.380
And the expected persistent files created with the old Tails version are present in the filesystem 1.708
And all persistent directories from the old Tails version have safe access rights 2.992
After features/support/hooks.rb:330 1.504
After features/support/hooks.rb:100 0.012
6:52.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.741
And no SquashFS delta is installed 0.224
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.560
When the network is plugged 0.075
And Tor is ready 21.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.896
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.742
Given I shutdown Tails and wait for the computer to power off 9.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.211
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.418
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.315
When the network is plugged 0.095
And Tor is ready 18.206
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.017
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.266
Given I shutdown Tails and wait for the computer to power off 6.601
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.681
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.082
And Tor is ready 22.383
Then the Upgrader considers the system as up-to-date 0.357
# 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 15.026
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.079
After features/support/hooks.rb:330 0.763
After features/support/hooks.rb:100 0.021
35.902
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.885
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.128
And Tor is ready 17.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.201
After features/support/hooks.rb:330 2.003
After features/support/hooks.rb:100 0.000