Project Number Date
test_Tails_ISO_stable 4949 16 Jul 2024, 21:07

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 18:23.653 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:10.525
Before features/support/hooks.rb:269 0.005
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.306
When I start Tails from USB drive "old" with network unplugged 1:34.977
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.025
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.129
Before features/support/hooks.rb:269 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:24.643
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.092
And I take note of which tps features are available 1.538
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.583
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.965
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:4.123
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.959
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.360
And I take note of which tps features are available 0.558
And I shutdown Tails and wait for the computer to power off 4.303
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.679
After features/support/hooks.rb:326 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.786
Before features/support/hooks.rb:269 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 10.211
And I log in to a new session 19.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.404
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.450
Then the running Tails is installed on USB drive "to_upgrade" 18.459
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 1.017
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.362
Before features/support/hooks.rb:269 0.004
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.508
Then all tps features from the old Tails version are active 1.516
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.932
And the expected persistent files created with the old Tails version are present in the filesystem 1.506
And all persistent directories from the old Tails version have safe access rights 2.431
After features/support/hooks.rb:326 0.828
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:13.103
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 11.379
And no SquashFS delta is installed 0.085
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.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.034
And Tor is ready 21.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.031
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.326
Given I shutdown Tails and wait for the computer to power off 8.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.366
Then Tails is running version 6.2~testoverlayfs 0.038
And all tps features are active 2.397
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.423
# 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.261
When the network is plugged 0.048
And Tor is ready 19.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.062
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.886
Given I shutdown Tails and wait for the computer to power off 4.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.888
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.373
When the network is plugged 0.042
And Tor is ready 19.756
Then the Upgrader considers the system as up-to-date 0.325
# 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.382
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.160
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.779
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.913
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 22.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.575
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.000