Project Number Date
test_Tails_ISO_stable 5326 11 Dec 2024, 08:37

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:13.958 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:5.578
Before features/support/hooks.rb:269 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.925
When I start Tails from USB drive "old" with network unplugged 1:28.519
Then the boot device has safe access rights 2.887
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 7.069
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.699
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:24.901
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 32.680
And I take note of which tps features are available 1.437
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.297
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.888
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.511
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.980
When I write some files expected to persist 1.866
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.610
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.989
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.039
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 11.053
And I log in to a new session 23.011
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.652
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.567
Then the running Tails is installed on USB drive "to_upgrade" 20.932
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 6.717
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.082
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.373
Then all tps features from the old Tails version are active 1.621
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.458
And the expected persistent files created with the old Tails version are present in the filesystem 1.523
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:28.450
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 10.906
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
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.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.075
And Tor is ready 21.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.892
Given I shutdown Tails and wait for the computer to power off 11.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.853
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.267
When the network is plugged 0.080
And Tor is ready 17.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.452
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.757
Given I shutdown Tails and wait for the computer to power off 13.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.965
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.991
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.103
And Tor is ready 20.272
Then the Upgrader considers the system as up-to-date 0.311
# 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.802
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.581
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.219
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 10.795
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.414
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.954
But a current signing key is available on our website 0.000
When the network is plugged 0.213
And Tor is ready 20.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.086
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.000