Project Number Date
test_Tails_ISO_stable 5201 20 Oct 2024, 12:26

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:43.688 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:22.987
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.697
When I start Tails from USB drive "old" with network unplugged 1:45.691
Then the boot device has safe access rights 3.219
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 7.249
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.797
Before features/support/hooks.rb:269 0.005
Given a computer 0.371
And I start Tails from USB drive "old" with network unplugged and I login 1:23.418
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 31.418
And I take note of which tps features are available 1.610
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 8.831
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.191
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.937
Then Tails is running from USB drive "old" 0.450
And all tps features are active 2.132
When I write some files expected to persist 2.165
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.435
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.332
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.454
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.260
Before features/support/hooks.rb:269 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 10.702
And I log in to a new session 23.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.745
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.714
Then the running Tails is installed on USB drive "to_upgrade" 25.702
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 6.903
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.125
Before features/support/hooks.rb:269 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:4.603
Then all tps features from the old Tails version are active 1.694
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.474
And the expected persistent files created with the old Tails version are present in the filesystem 1.398
And all persistent directories from the old Tails version have safe access rights 2.445
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:32.908
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.006
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.809
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.073
And Tor is ready 23.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.065
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.892
Given I shutdown Tails and wait for the computer to power off 8.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.889
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.278
When the network is plugged 0.082
And Tor is ready 19.769
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.110
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.104
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.938
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.311
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.353
When the network is plugged 0.073
And Tor is ready 21.017
Then the Upgrader considers the system as up-to-date 0.303
# 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.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.063
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.416
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 10.760
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 1.637
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 22.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.130
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.000