Project Number Date
test_Tails_ISO_stable 5348 20 Dec 2024, 08:40

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:8.910 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:14.218
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.134
When I start Tails from USB drive "old" with network unplugged 1:37.223
Then the boot device has safe access rights 3.438
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.377
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 7.247
After features/support/hooks.rb:100 0.014
Tags: @product
2:10.085
Before features/support/hooks.rb:269 0.006
Given a computer 0.533
And I start Tails from USB drive "old" with network unplugged and I login 1:26.303
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 32.134
And I take note of which tps features are available 1.536
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
3:11.900
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.067
Then Tails is running from USB drive "old" 0.419
And all tps features are active 2.123
When I write some files expected to persist 1.844
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.496
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.393
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.296
After features/support/hooks.rb:326 0.095
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.328
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 11.996
And I log in to a new session 19.938
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.814
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.132
Then the running Tails is installed on USB drive "to_upgrade" 25.581
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 2.029
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.140
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.444
Then all tps features from the old Tails version are active 2.013
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.237
And the expected persistent files created with the old Tails version are present in the filesystem 1.498
And all persistent directories from the old Tails version have safe access rights 2.414
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:43.791
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 15.072
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.141
And Tor is ready 24.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.530
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.854
Given I shutdown Tails and wait for the computer to power off 11.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.387
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.391
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
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.325
# 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.277
When the network is plugged 0.087
And Tor is ready 19.902
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.987
Given I shutdown Tails and wait for the computer to power off 4.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.366
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 0.089
And Tor is ready 20.277
Then the Upgrader considers the system as up-to-date 0.312
# 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.816
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.913
After features/support/hooks.rb:326 0.935
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
1:1.444
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.933
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 49.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.000