Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 10 21 Apr 2025, 21:15

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:50.930 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:11.429
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.296
When I start Tails from USB drive "old" with network unplugged 1:35.858
Then the boot device has safe access rights 2.950
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 6.821
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:27.963
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 31.008
And I take note of which tps features are available 1.666
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.205
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.831
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.097
When I write some files expected to persist 2.174
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.654
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.485
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.840
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.665
And I log in to a new session 18.358
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.705
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.380
Then the running Tails is installed on USB drive "to_upgrade" 26.883
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 1.162
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.993
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.273
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:330 1.321
After features/support/hooks.rb:100 0.007
6:44.978
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.931
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.334
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.068
And Tor is ready 24.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.977
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.257
Given I shutdown Tails and wait for the computer to power off 8.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.098
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.376
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.389
# 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.283
When the network is plugged 0.069
And Tor is ready 19.854
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.636
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.545
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.263
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.062
And Tor is ready 20.017
Then the Upgrader considers the system as up-to-date 0.368
# 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 16.198
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.721
After features/support/hooks.rb:330 0.744
After features/support/hooks.rb:100 0.015
42.681
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 10.634
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 24.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.807
After features/support/hooks.rb:330 1.123
After features/support/hooks.rb:100 0.000