Project Number Date
test_Tails_ISO_tca-remove-cruft 5 12 May 2025, 09:54

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 18:46.484 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:54.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.075
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.667
When I start Tails from USB drive "old" with network unplugged 1:19.929
Then the boot device has safe access rights 2.997
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 6.960
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:22.644
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 30.758
And I take note of which tps features are available 2.327
Then a Tails persistence partition exists on USB drive "old" 0.751
And I shutdown Tails and wait for the computer to power off 8.260
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
3:11.242
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 "old" with network unplugged and I login with persistence enabled 2:31.736
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.376
When I write some files expected to persist 2.677
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 3.628
And I take note of which tps features are available 0.609
And I shutdown Tails and wait for the computer to power off 4.544
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.385
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.093
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 11.936
And I log in to a new session 19.380
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.825
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.684
Then the running Tails is installed on USB drive "to_upgrade" 19.416
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.158
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.233
Then all tps features from the old Tails version are active 1.670
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.300
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:330 0.979
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:19.293
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 11.027
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545
When the network is plugged 0.072
And Tor is ready 18.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.004
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.129
Given I shutdown Tails and wait for the computer to power off 8.601
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.850
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.049
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.254
When the network is plugged 0.071
And Tor is ready 18.454
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.561
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.685
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.875
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.884
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.081
And Tor is ready 19.111
Then the Upgrader considers the system as up-to-date 0.311
# 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.013
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.748
After features/support/hooks.rb:330 0.757
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.256
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 10.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 17.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.890
After features/support/hooks.rb:330 0.694
After features/support/hooks.rb:100 0.000