Project Number Date
test_Tails_ISO_stable 5319 07 Dec 2024, 08:41

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:31.471 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:15.718
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 39.432
When I start Tails from USB drive "old" with network unplugged 1:30.556
Then the boot device has safe access rights 3.317
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.259
After features/support/hooks.rb:326 3.555
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.028
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:28.119
Then Tails is running from USB drive "old" 0.472
And I create a persistent partition 33.354
And I take note of which tps features are available 1.755
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.287
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.905
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.044
Then Tails is running from USB drive "old" 1.447
And all tps features are active 2.141
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.422
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.501
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.910
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 10.389
And I log in to a new session 18.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.596
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.035
Then the running Tails is installed on USB drive "to_upgrade" 22.565
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.053
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.132
Before features/support/hooks.rb:269 0.008
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.641
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.538
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.373
After features/support/hooks.rb:326 0.837
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:32.917
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.352
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.063
And Tor is ready 20.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.201
Given I shutdown Tails and wait for the computer to power off 8.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.716
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.695
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.325
When the network is plugged 0.093
And Tor is ready 17.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.465
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.872
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.470
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.052
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.079
And Tor is ready 19.025
Then the Upgrader considers the system as up-to-date 10.881
# 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.942
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.355
After features/support/hooks.rb:326 0.814
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.858
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.874
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 16.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.534
After features/support/hooks.rb:326 1.685
After features/support/hooks.rb:100 0.000