Project Number Date
test_Tails_ISO_stable 5276 18 Nov 2024, 12:53

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:19.125 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:29.608
Before features/support/hooks.rb:269 0.008
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 31.427
When I start Tails from USB drive "old" with network unplugged 1:52.055
Then the boot device has safe access rights 3.671
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.558
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.395
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:31.264
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 34.812
And I take note of which tps features are available 1.306
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 6.575
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.602
Before features/support/hooks.rb:269 0.005
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.665
Then Tails is running from USB drive "old" 0.600
And all tps features are active 2.395
When I write some files expected to persist 1.862
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.979
And I take note of which tps features are available 0.664
And I shutdown Tails and wait for the computer to power off 4.125
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.359
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.012
Tags: @product
2:33.413
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.168
And I log in to a new session 19.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.830
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.919
Then the running Tails is installed on USB drive "to_upgrade" 19.165
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.605
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.886
Before features/support/hooks.rb:269 0.017
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.794
Then all tps features from the old Tails version are active 1.779
And Tails is running from USB drive "to_upgrade" 0.422
And the boot device has safe access rights 3.567
And the expected persistent files created with the old Tails version are present in the filesystem 1.572
And all persistent directories from the old Tails version have safe access rights 2.539
After features/support/hooks.rb:326 0.848
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:58.545
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.807
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.500
When the network is plugged 0.068
And Tor is ready 48.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.307
Given I shutdown Tails and wait for the computer to power off 10.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.517
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.314
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.323
When the network is plugged 0.076
And Tor is ready 21.081
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.694
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.556
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.123
And the file system changes introduced in version 6.3~testoverlayfs are present 0.602
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.074
And Tor is ready 19.156
Then the Upgrader considers the system as up-to-date 0.334
# 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 15.224
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.059
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.672
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.227
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 1.057
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.845
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.000