Project Number Date
test_Tails_ISO_tca-remove-cruft 10 17 May 2025, 10:09

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:53.942 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:7.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 34.529
When I start Tails from USB drive "old" with network unplugged 1:27.560
Then the boot device has safe access rights 3.253
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 1.087
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:29.225
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 31.775
And I take note of which tps features are available 2.462
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 10.653
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.008
Tags: @product
3:16.642
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.540
Then Tails is running from USB drive "old" 1.063
And all tps features are active 2.046
When I write some files expected to persist 3.379
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 3.126
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 6.674
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.496
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.007
Tags: @product
2:35.070
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.130
And I log in to a new session 21.999
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.471
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.545
Then the running Tails is installed on USB drive "to_upgrade" 25.102
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 2.437
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.700
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.110
Then all tps features from the old Tails version are active 1.579
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.391
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.619
After features/support/hooks.rb:330 1.373
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:44.493
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 13.681
And no SquashFS delta is installed 0.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.524
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.107
And Tor is ready 23.478
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.640
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.717
Given I shutdown Tails and wait for the computer to power off 17.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.385
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.642
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.276
When the network is plugged 0.074
And Tor is ready 48.484
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.620
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.987
Given I shutdown Tails and wait for the computer to power off 4.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.683
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.563
And the file system changes introduced in version 6.3~testoverlayfs are present 0.642
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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.087
And Tor is ready 19.530
Then the Upgrader considers the system as up-to-date 10.808
# 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.088
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.424
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.960
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.315
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.600
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 20.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.940
After features/support/hooks.rb:330 1.553
After features/support/hooks.rb:100 0.000