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

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:3.310 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:21.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.825
When I start Tails from USB drive "old" with network unplugged 1:44.474
Then the boot device has safe access rights 3.419
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:330 6.982
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.072
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:28.353
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 33.082
And I take note of which tps features are available 2.456
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.690
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.757
Then Tails is running from USB drive "old" 1.797
And all tps features are active 2.084
When I write some files expected to persist 4.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.569
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 6.227
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.353
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.608
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 13.332
And I log in to a new session 18.875
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.572
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.631
Then the running Tails is installed on USB drive "to_upgrade" 22.217
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:330 0.987
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.237
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.125
Then all tps features from the old Tails version are active 1.680
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.706
And the expected persistent files created with the old Tails version are present in the filesystem 1.595
And all persistent directories from the old Tails version have safe access rights 2.554
After features/support/hooks.rb:330 1.287
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.940
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.321
And no SquashFS delta is installed 0.418
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.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.088
And Tor is ready 20.141
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.136
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.556
Given I shutdown Tails and wait for the computer to power off 8.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.617
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.259
# 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.315
When the network is plugged 0.071
And Tor is ready 18.447
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.219
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.130
Given I shutdown Tails and wait for the computer to power off 4.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.916
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.327
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.248
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.072
And Tor is ready 17.067
Then the Upgrader considers the system as up-to-date 10.885
# 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.701
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.514
After features/support/hooks.rb:330 0.702
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
37.884
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 9.685
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.526
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 18.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.585
After features/support/hooks.rb:330 1.821
After features/support/hooks.rb:100 0.000