Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 2 15 Apr 2025, 20:56

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:35.457 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:56.237
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.782
When I start Tails from USB drive "old" with network unplugged 1:21.351
Then the boot device has safe access rights 2.877
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 6.938
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.052
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:23.185
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 30.605
And I take note of which tps features are available 1.702
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.214
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.678
Then Tails is running from USB drive "old" 1.436
And all tps features are active 1.825
When I write some files expected to persist 1.568
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 3.134
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.672
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.932
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.736
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 10.261
And I log in to a new session 17.489
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.057
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.249
Then the running Tails is installed on USB drive "to_upgrade" 21.721
And I unplug USB drive "to_upgrade" 0.276
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 1.121
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.477
Then all tps features from the old Tails version are active 1.628
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.342
And the expected persistent files created with the old Tails version are present in the filesystem 1.767
And all persistent directories from the old Tails version have safe access rights 2.505
After features/support/hooks.rb:330 1.292
After features/support/hooks.rb:100 0.011
7:27.155
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.912
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.456
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.617
When the network is plugged 0.065
And Tor is ready 20.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.117
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.999
Given I shutdown Tails and wait for the computer to power off 8.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.435
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.404
# 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.430
When the network is plugged 0.076
And Tor is ready 19.561
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.898
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.151
Given I shutdown Tails and wait for the computer to power off 1:0.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.217
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.054
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.071
And Tor is ready 19.561
Then the Upgrader considers the system as up-to-date 0.322
# 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.579
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.552
After features/support/hooks.rb:330 0.679
After features/support/hooks.rb:100 0.015
36.507
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.742
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 18.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.211
After features/support/hooks.rb:330 1.382
After features/support/hooks.rb:100 0.000