Project Number Date
test_Tails_ISO_stable 5461 16 Feb 2025, 12:30

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:52.279 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:36.227
Before features/support/hooks.rb:269 0.005
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.893
When I start Tails from USB drive "old" with network unplugged 2:0.564
Then the boot device has safe access rights 3.416
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.178
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:23.142
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 32.478
And I take note of which tps features are available 1.370
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.761
After features/support/hooks.rb:326 0.212
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.967
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.501
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.209
When I write some files expected to persist 1.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.325
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 4.175
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.299
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.607
Before features/support/hooks.rb:269 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 9.884
And I log in to a new session 19.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.632
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.368
Then the running Tails is installed on USB drive "to_upgrade" 23.594
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:326 2.296
After features/support/hooks.rb:100 0.000
Tags: @product
2:43.372
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:33.062
Then all tps features from the old Tails version are active 2.195
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.254
And the expected persistent files created with the old Tails version are present in the filesystem 1.811
And all persistent directories from the old Tails version have safe access rights 2.488
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:15.459
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.703
And no SquashFS delta is installed 0.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.813
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.065
And Tor is ready 53.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.954
Given I shutdown Tails and wait for the computer to power off 8.736
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.816
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.282
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.375
When the network is plugged 0.077
And Tor is ready 21.686
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.476
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.878
Given I shutdown Tails and wait for the computer to power off 4.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.707
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.060
And Tor is ready 19.745
Then the Upgrader considers the system as up-to-date 0.349
# 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 14.868
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
43.466
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.997
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.591
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.055
But a current signing key is available on our website 0.000
When the network is plugged 0.358
And Tor is ready 24.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.861
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.000