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

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:7.443 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:53.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.943
When I start Tails from USB drive "old" with network unplugged 1:19.861
Then the boot device has safe access rights 2.882
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.515
After features/support/hooks.rb:100 0.013
Tags: @product
2:5.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:22.490
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 31.118
And I take note of which tps features are available 1.839
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 9.066
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.335
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.452
Then Tails is running from USB drive "old" 1.059
And all tps features are active 2.082
When I write some files expected to persist 1.748
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 3.887
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 6.426
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.606
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.016
Tags: @product
2:34.216
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 10.358
And I log in to a new session 19.733
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.739
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.760
Then the running Tails is installed on USB drive "to_upgrade" 26.826
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 1.981
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.130
Then all tps features from the old Tails version are active 1.653
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.242
And the expected persistent files created with the old Tails version are present in the filesystem 1.342
And all persistent directories from the old Tails version have safe access rights 2.301
After features/support/hooks.rb:330 1.354
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:46.271
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 11.261
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.066
And Tor is ready 47.722
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.561
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.205
Given I shutdown Tails and wait for the computer to power off 10.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.370
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.989
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.305
When the network is plugged 0.074
And Tor is ready 16.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.634
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.881
Given I shutdown Tails and wait for the computer to power off 4.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.795
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.958
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.073
And Tor is ready 17.809
Then the Upgrader considers the system as up-to-date 0.302
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.519
After features/support/hooks.rb:330 0.802
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.301
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.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
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.076
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.857
After features/support/hooks.rb:330 1.045
After features/support/hooks.rb:100 0.000