Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 1 05 Mar 2025, 21:16

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 22:6.223 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:21.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.445
And I create a 7200 MiB disk named "old" 0.265
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 32.253
When I start Tails from USB drive "old" with network unplugged 1:42.427
Then the boot device has safe access rights 3.427
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 7.084
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:35.250
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 31.991
And I take note of which tps features are available 1.905
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.680
After features/support/hooks.rb:330 0.262
After features/support/hooks.rb:100 0.009
Tags: @product
3:17.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.825
Then Tails is running from USB drive "old" 0.729
And all tps features are active 2.056
When I write some files expected to persist 1.974
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 3.294
And I take note of which tps features are available 0.592
And I shutdown Tails and wait for the computer to power off 6.595
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.484
After features/support/hooks.rb:330 0.215
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.282
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.077
And I log in to a new session 19.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.872
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.419
Then the running Tails is installed on USB drive "to_upgrade" 24.034
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 2.060
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.368
Then all tps features from the old Tails version are active 1.985
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.985
And the expected persistent files created with the old Tails version are present in the filesystem 1.783
And all persistent directories from the old Tails version have safe access rights 2.982
After features/support/hooks.rb:330 1.737
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:18.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.790
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.124
And Tor is ready 23.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.646
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.445
Given I shutdown Tails and wait for the computer to power off 1:23.630
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.689
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.062
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.370
When the network is plugged 0.068
And Tor is ready 19.068
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.060
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.083
Given I shutdown Tails and wait for the computer to power off 4.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.020
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.229
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.115
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.087
And Tor is ready 17.897
Then the Upgrader considers the system as up-to-date 10.915
# 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.723
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.937
After features/support/hooks.rb:330 0.911
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.319
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 10.285
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.030
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.260
But a current signing key is available on our website 0.000
When the network is plugged 0.487
And Tor is ready 22.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.792
After features/support/hooks.rb:330 0.687
After features/support/hooks.rb:100 0.000