Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 25 26 Mar 2025, 00:14

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:23.830 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:10.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.286
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.603
When I start Tails from USB drive "old" with network unplugged 1:33.826
Then the boot device has safe access rights 3.185
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.105
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 7.196
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:21.400
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 28.894
And I take note of which tps features are available 1.750
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.267
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.387
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.424
Then Tails is running from USB drive "old" 0.577
And all tps features are active 2.030
When I write some files expected to persist 1.696
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.796
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 6.223
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.285
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.634
And I log in to a new session 17.793
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.452
Then the running Tails is installed on USB drive "to_upgrade" 21.463
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 2.209
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.240
Then all tps features from the old Tails version are active 2.014
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.398
And the expected persistent files created with the old Tails version are present in the filesystem 1.646
And all persistent directories from the old Tails version have safe access rights 2.476
After features/support/hooks.rb:330 1.810
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:58.327
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 12.152
And no SquashFS delta is installed 0.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.390
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.069
And Tor is ready 49.686
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.777
Given I shutdown Tails and wait for the computer to power off 8.647
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.546
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.162
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.246
When the network is plugged 0.060
And Tor is ready 20.912
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.169
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.379
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.977
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.079
And Tor is ready 18.455
Then the Upgrader considers the system as up-to-date 0.317
# 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.759
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
36.270
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 10.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.717
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.249
And the signing key used by the Upgrader is outdated 0.131
But a current signing key is available on our website 0.000
When the network is plugged 0.130
And Tor is ready 20.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.797
After features/support/hooks.rb:330 1.679
After features/support/hooks.rb:100 0.000