Project Number Date
test_Tails_ISO_stable 4863 31 May 2024, 02:25

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:7.759 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:3.356
Before features/support/hooks.rb:265 0.008
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.680
When I start Tails from USB drive "old" with network unplugged 1:26.154
Then the boot device has safe access rights 3.186
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:311 9.358
After features/support/hooks.rb:100 0.019
Tags: @product
2:9.179
Before features/support/hooks.rb:265 0.012
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:21.448
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 35.417
And I take note of which tps features are available 2.047
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.837
After features/support/hooks.rb:311 0.150
After features/support/hooks.rb:100 0.012
Tags: @product
2:59.460
Before features/support/hooks.rb:265 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.893
Then Tails is running from USB drive "old" 0.420
And all tps features are active 1.994
When I write some files expected to persist 1.749
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.973
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.329
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.804
After features/support/hooks.rb:311 0.164
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.616
Before features/support/hooks.rb:265 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.502
And I log in to a new session 18.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.629
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.931
Then the running Tails is installed on USB drive "to_upgrade" 18.413
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:311 6.649
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.098
Before features/support/hooks.rb:265 0.009
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.564
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.524
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.244
After features/support/hooks.rb:311 0.774
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:36.443
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.830
And no SquashFS delta is installed 0.488
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.440
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.465
When the network is plugged 0.048
And Tor is ready 18.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.399
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.647
Given I shutdown Tails and wait for the computer to power off 8.656
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.769
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.154
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.412
# 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.301
When the network is plugged 0.046
And Tor is ready 19.733
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.707
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.015
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.463
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.051
And Tor is ready 17.966
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 14.714
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.901
After features/support/hooks.rb:311 0.726
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
32.605
Before features/support/hooks.rb:265 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.705
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.051
And the signing key used by the Upgrader is outdated 1.071
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 14.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.866
After features/support/hooks.rb:311 0.852
After features/support/hooks.rb:100 0.000