Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 13 24 Apr 2025, 21:28

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 20:11.434 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:43.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 1:6.473
When I start Tails from USB drive "old" with network unplugged 1:31.188
Then the boot device has safe access rights 3.107
And Tails is running from USB drive "old" 0.463
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 3.719
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:27.096
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 31.107
And I take note of which tps features are available 1.721
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.321
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.941
Then Tails is running from USB drive "old" 0.985
And all tps features are active 1.969
When I write some files expected to persist 1.740
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 3.250
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 6.564
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.715
After features/support/hooks.rb:330 0.101
After features/support/hooks.rb:100 0.014
Tags: @product
2:39.861
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.525
And I log in to a new session 20.062
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.934
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.883
Then the running Tails is installed on USB drive "to_upgrade" 27.555
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 2.082
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.943
Then all tps features from the old Tails version are active 1.569
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.537
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 2.523
After features/support/hooks.rb:330 1.052
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:47.660
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 with a persistent partition enabled and logged in 25.331
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.057
And Tor is ready 21.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.543
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.836
Given I shutdown Tails and wait for the computer to power off 9.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.143
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.354
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.285
When the network is plugged 0.081
And Tor is ready 20.901
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.649
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.273
Given I shutdown Tails and wait for the computer to power off 4.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.139
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.376
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.074
And Tor is ready 16.927
Then the Upgrader considers the system as up-to-date 0.303
# 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 17.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.336
After features/support/hooks.rb:330 0.950
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.956
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 9.845
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.441
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.135
After features/support/hooks.rb:330 1.000
After features/support/hooks.rb:100 0.000