Project Number Date
test_Tails_ISO_tca-remove-cruft 1 08 May 2025, 14:07

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:39.068 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:4.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.422
When I start Tails from USB drive "old" with network unplugged 1:27.246
Then the boot device has safe access rights 3.105
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 6.888
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:32.440
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 29.998
And I take note of which tps features are available 2.172
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 8.237
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.471
Then Tails is running from USB drive "old" 0.716
And all tps features are active 2.180
When I write some files expected to persist 1.656
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 3.632
And I take note of which tps features are available 0.440
And I shutdown Tails and wait for the computer to power off 6.184
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.733
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.393
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 24.391
And I log in to a new session 18.051
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.983
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.478
Then the running Tails is installed on USB drive "to_upgrade" 24.584
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 2.144
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.201
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.311
Then all tps features from the old Tails version are active 1.770
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.748
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:330 1.344
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
6:32.987
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 12.185
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.425
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.072
And Tor is ready 22.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.878
Given I shutdown Tails and wait for the computer to power off 8.736
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.560
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.992
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.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.271
When the network is plugged 0.062
And Tor is ready 20.468
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.013
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.440
Given I shutdown Tails and wait for the computer to power off 4.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.206
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.147
And Tor is ready 16.931
Then the Upgrader considers the system as up-to-date 0.419
# 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.669
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.861
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.324
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 9.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.077
And Tor is ready 21.901
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.853
After features/support/hooks.rb:330 0.673
After features/support/hooks.rb:100 0.000