Project Number Date
test_Tails_ISO_stable 5341 17 Dec 2024, 12:44

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:31.086 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:12.029
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.075
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.475
When I start Tails from USB drive "old" with network unplugged 1:36.082
Then the boot device has safe access rights 3.115
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.521
After features/support/hooks.rb:100 0.023
Tags: @product
2:6.093
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:23.103
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.711
And I take note of which tps features are available 1.443
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.484
After features/support/hooks.rb:326 0.233
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.062
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.511
Then Tails is running from USB drive "old" 1.201
And all tps features are active 2.106
When I write some files expected to persist 2.490
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 3.092
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.309
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.131
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.200
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.573
And I log in to a new session 21.126
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.584
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.989
Then the running Tails is installed on USB drive "to_upgrade" 20.037
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.132
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.094
Before features/support/hooks.rb:269 0.006
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.222
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.201
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 2.795
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:37.845
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.826
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.067
And Tor is ready 22.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.079
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.462
Given I shutdown Tails and wait for the computer to power off 1:16.875
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.203
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
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.320
# 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.293
When the network is plugged 0.091
And Tor is ready 16.041
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.727
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.952
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.519
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.920
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.065
And Tor is ready 16.752
Then the Upgrader considers the system as up-to-date 10.847
# 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.605
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.951
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.760
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.037
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.814
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 21.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.642
After features/support/hooks.rb:326 1.001
After features/support/hooks.rb:100 0.000