Project Number Date
test_Tails_ISO_devel 3768 06 Apr 2025, 13:04

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:57.698 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:29.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.104
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 38.544
When I start Tails from USB drive "old" with network unplugged 1:44.906
Then the boot device has safe access rights 3.292
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 4.197
After features/support/hooks.rb:100 0.065
Tags: @product
2:14.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.041
Given a computer 0.415
And I start Tails from USB drive "old" with network unplugged and I login 1:31.572
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 30.980
And I take note of which tps features are available 1.874
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.360
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.159
Then Tails is running from USB drive "old" 0.558
And all tps features are active 1.954
When I write some files expected to persist 1.757
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 2.907
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.422
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.421
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.159
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 9.753
And I log in to a new session 19.195
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.088
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.969
Then the running Tails is installed on USB drive "to_upgrade" 22.319
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 2.369
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.960
Then all tps features from the old Tails version are active 1.702
And Tails is running from USB drive "to_upgrade" 0.335
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.830
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:330 1.314
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
6:41.222
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.210
And no SquashFS delta is installed 0.220
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.391
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.062
And Tor is ready 18.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.851
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.310
Given I shutdown Tails and wait for the computer to power off 9.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.583
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.400
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
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.326
# 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.399
When the network is plugged 0.087
And Tor is ready 22.335
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.225
Given I shutdown Tails and wait for the computer to power off 4.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.356
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.285
When the network is plugged 0.071
And Tor is ready 20.018
Then the Upgrader considers the system as up-to-date 0.300
# 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.402
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.103
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
42.117
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 13.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
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.091
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 21.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.204
After features/support/hooks.rb:330 1.105
After features/support/hooks.rb:100 0.000