Project Number Date
test_Tails_ISO_tca-misc-improvements 16 23 Apr 2025, 18:44

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 21:50.599 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.464
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.042
When I start Tails from USB drive "old" with network unplugged 1:32.889
Then the boot device has safe access rights 3.176
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 3.973
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.365
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.468
And I start Tails from USB drive "old" with network unplugged and I login 1:29.263
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 31.259
And I take note of which tps features are available 2.546
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.690
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
3:11.489
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 with persistence enabled 2:33.637
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.302
When I write some files expected to persist 1.934
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.569
And all persistent directories from the old Tails version have safe access rights 2.967
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.617
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.007
Tags: @product
3:8.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.175
And I log in to a new session 19.782
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.845
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.168
Then the running Tails is installed on USB drive "to_upgrade" 35.659
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.271
After features/support/hooks.rb:330 1.352
After features/support/hooks.rb:100 0.000
Tags: @product
2:49.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.265
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:37.901
Then all tps features from the old Tails version are active 2.505
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.919
And the expected persistent files created with the old Tails version are present in the filesystem 1.576
And all persistent directories from the old Tails version have safe access rights 2.634
After features/support/hooks.rb:330 1.021
After features/support/hooks.rb:100 0.010
7:36.978
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 30.938
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.553
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.474
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.095
And Tor is ready 23.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.564
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.034
Given I shutdown Tails and wait for the computer to power off 9.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.984
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.524
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.327
When the network is plugged 0.091
And Tor is ready 19.526
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.565
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.432
Given I shutdown Tails and wait for the computer to power off 6.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.172
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.372
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.095
And Tor is ready 22.267
Then the Upgrader considers the system as up-to-date 0.334
# 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.253
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.856
After features/support/hooks.rb:330 0.850
After features/support/hooks.rb:100 0.026
40.534
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 13.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
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.726
And Tor is ready 18.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.154
After features/support/hooks.rb:330 1.396
After features/support/hooks.rb:100 0.000