Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 23 23 Mar 2025, 21:37

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:51.431 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:6.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.664
When I start Tails from USB drive "old" with network unplugged 1:31.937
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 7.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:22.656
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 31.184
And I take note of which tps features are available 1.433
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 8.574
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.141
Then Tails is running from USB drive "old" 0.632
And all tps features are active 1.883
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.206
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.082
After features/support/hooks.rb:330 0.083
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.638
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 without a persistent partition and stopped at Tails Greeter's login screen 9.781
And I log in to a new session 17.965
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.419
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.192
Then the running Tails is installed on USB drive "to_upgrade" 21.464
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 1.689
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.902
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.307
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.319
After features/support/hooks.rb:330 1.365
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
6:23.027
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 12.301
And no SquashFS delta is installed 0.927
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
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.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.073
And Tor is ready 23.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.882
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.801
Given I shutdown Tails and wait for the computer to power off 8.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.717
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.273
When the network is plugged 0.076
And Tor is ready 15.843
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.590
Given I shutdown Tails and wait for the computer to power off 4.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.903
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.080
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.107
And Tor is ready 19.890
Then the Upgrader considers the system as up-to-date 0.298
# 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.010
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.936
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.400
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.272
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.082
After features/support/hooks.rb:330 0.843
After features/support/hooks.rb:100 0.000