Project Number Date
test_Tails_ISO_tca-remove-cruft 4 11 May 2025, 09:50

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:15.916 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:9.246
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.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.625
When I start Tails from USB drive "old" with network unplugged 1:33.362
Then the boot device has safe access rights 2.914
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 0.899
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:21.657
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 31.074
And I take note of which tps features are available 1.779
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.233
After features/support/hooks.rb:330 0.210
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.470
Then Tails is running from USB drive "old" 0.453
And all tps features are active 2.047
When I write some files expected to persist 1.619
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.452
And I take note of which tps features are available 0.589
And I shutdown Tails and wait for the computer to power off 4.699
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.350
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.060
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 without a persistent partition and stopped at Tails Greeter's login screen 23.470
And I log in to a new session 18.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.750
And I plug USB drive "to_upgrade" 2.518
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.393
Then the running Tails is installed on USB drive "to_upgrade" 25.976
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 1.985
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.847
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:5.482
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.338
And the expected persistent files created with the old Tails version are present in the filesystem 1.506
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:330 1.053
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
6:34.117
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 with a persistent partition enabled and logged in 11.945
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.077
And Tor is ready 23.509
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.659
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.261
Given I shutdown Tails and wait for the computer to power off 8.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.726
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.948
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
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.373
# 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.285
When the network is plugged 0.086
And Tor is ready 18.761
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.919
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.681
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.437
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.086
And Tor is ready 17.335
Then the Upgrader considers the system as up-to-date 10.728
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.460
After features/support/hooks.rb:330 0.680
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
43.106
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.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 25.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.258
After features/support/hooks.rb:330 0.624
After features/support/hooks.rb:100 0.000