Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 21 21 Mar 2025, 22:10

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:23.273 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
1:51.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 28.636
When I start Tails from USB drive "old" with network unplugged 1:17.638
Then the boot device has safe access rights 3.142
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.498
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:18.752
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.154
And I take note of which tps features are available 1.295
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.807
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.969
When I write some files expected to persist 1.641
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.465
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.904
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.914
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.443
And I log in to a new session 17.204
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.434
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.800
Then the running Tails is installed on USB drive "to_upgrade" 19.159
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 1.862
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.511
Then all tps features from the old Tails version are active 1.912
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.107
And the expected persistent files created with the old Tails version are present in the filesystem 1.654
And all persistent directories from the old Tails version have safe access rights 2.883
After features/support/hooks.rb:330 1.379
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:15.952
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 with a persistent partition enabled and logged in 13.714
And no SquashFS delta is installed 0.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.163
And Tor is ready 22.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.042
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.126
Given I shutdown Tails and wait for the computer to power off 8.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.936
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.987
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.236
When the network is plugged 0.095
And Tor is ready 24.063
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.759
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.541
Given I shutdown Tails and wait for the computer to power off 4.294
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.943
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.063
And Tor is ready 18.137
Then the Upgrader considers the system as up-to-date 0.343
# 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.981
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.940
After features/support/hooks.rb:330 0.764
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
35.578
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 with a persistent partition enabled and logged in 9.876
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 18.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.243
After features/support/hooks.rb:330 0.882
After features/support/hooks.rb:100 0.000