Project Number Date
test_Tails_ISO_tca-remove-cruft 7 14 May 2025, 09:49

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:41.932 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:0.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.665
When I start Tails from USB drive "old" with network unplugged 1:26.333
Then the boot device has safe access rights 2.815
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 6.840
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:21.927
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 30.148
And I take note of which tps features are available 1.640
Then a Tails persistence partition exists on USB drive "old" 0.692
And I shutdown Tails and wait for the computer to power off 8.151
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.246
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 with persistence enabled 2:12.333
Then Tails is running from USB drive "old" 0.319
And all tps features are active 2.013
When I write some files expected to persist 1.603
# 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.359
And all persistent directories from the old Tails version have safe access rights 2.300
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.621
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.853
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.905
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 without a persistent partition and stopped at Tails Greeter's login screen 10.062
And I log in to a new session 18.612
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.496
And I plug USB drive "to_upgrade" 2.473
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.982
Then the running Tails is installed on USB drive "to_upgrade" 24.850
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 1.838
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.567
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.350
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.401
After features/support/hooks.rb:330 1.316
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:30.419
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 12.330
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.078
And Tor is ready 21.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.423
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.639
Given I shutdown Tails and wait for the computer to power off 8.510
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.741
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.243
When the network is plugged 0.065
And Tor is ready 47.012
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.554
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.842
Given I shutdown Tails and wait for the computer to power off 4.616
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.364
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.911
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
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.269
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.069
And Tor is ready 18.634
Then the Upgrader considers the system as up-to-date 0.306
# 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 15.610
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.042
After features/support/hooks.rb:330 0.671
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.429
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 10.453
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.889
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 16.415
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.408
After features/support/hooks.rb:330 1.941
After features/support/hooks.rb:100 0.000