Project Number Date
test_Tails_ISO_stable 5647 14 May 2025, 13:05

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 21:14.275 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:23.026
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.277
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 35.832
When I start Tails from USB drive "old" with network unplugged 1:40.585
Then the boot device has safe access rights 3.579
And Tails is running from USB drive "old" 0.774
And there is no persistence partition on USB drive "old" 0.103
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.287
After features/support/hooks.rb:330 3.760
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:31.631
Then Tails is running from USB drive "old" 0.478
And I create a persistent partition 35.021
And I take note of which tps features are available 1.957
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.784
After features/support/hooks.rb:330 0.339
After features/support/hooks.rb:100 0.025
Tags: @product
3:12.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.429
Then Tails is running from USB drive "old" 0.428
And all tps features are active 2.462
When I write some files expected to persist 2.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.502
And all persistent directories from the old Tails version have safe access rights 2.663
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.503
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.279
After features/support/hooks.rb:330 0.091
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.863
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 without a persistent partition and stopped at Tails Greeter's login screen 12.822
And I log in to a new session 22.100
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.565
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.494
Then the running Tails is installed on USB drive "to_upgrade" 25.974
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 3.716
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.636
Then all tps features from the old Tails version are active 1.911
And Tails is running from USB drive "to_upgrade" 0.467
And the boot device has safe access rights 3.327
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:330 1.449
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
7:29.492
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 12.932
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.154
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.670
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.569
When the network is plugged 0.070
And Tor is ready 23.161
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.082
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.734
Given I shutdown Tails and wait for the computer to power off 11.980
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.129
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.511
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
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.312
# 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.283
When the network is plugged 0.082
And Tor is ready 18.786
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.959
Given I shutdown Tails and wait for the computer to power off 6.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.265
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.282
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.332
When the network is plugged 0.064
And Tor is ready 50.539
Then the Upgrader considers the system as up-to-date 0.292
# 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.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.133
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.471
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.756
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.134
And Tor is ready 20.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.978
After features/support/hooks.rb:330 1.585
After features/support/hooks.rb:100 0.000