Project Number Date
test_Tails_ISO_devel 3423 10 Jun 2024, 12:43

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:36.182 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:1.080
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 28.475
When I start Tails from USB drive "old" with network unplugged 1:27.114
Then the boot device has safe access rights 3.055
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:315 3.566
After features/support/hooks.rb:100 0.086
Tags: @product
2:6.431
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:20.352
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 34.639
And I take note of which tps features are available 1.695
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.434
After features/support/hooks.rb:315 0.160
After features/support/hooks.rb:100 0.013
Tags: @product
2:51.835
Before features/support/hooks.rb:269 0.008
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.091
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.107
When I write some files expected to persist 2.989
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.592
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.142
After features/support/hooks.rb:315 0.095
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.267
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 11.642
And I log in to a new session 19.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.380
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.082
Then the running Tails is installed on USB drive "to_upgrade" 16.391
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:315 6.561
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.069
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.837
Then all tps features from the old Tails version are active 1.779
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.478
And the expected persistent files created with the old Tails version are present in the filesystem 1.826
And all persistent directories from the old Tails version have safe access rights 2.610
After features/support/hooks.rb:315 1.094
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:8.309
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.239
And no SquashFS delta is installed 0.469
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.053
And Tor is ready 21.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.490
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.353
Given I shutdown Tails and wait for the computer to power off 8.940
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.009
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.630
And the file system changes introduced in version 6.2~testoverlayfs are present 0.407
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.286
When the network is plugged 0.039
And Tor is ready 20.487
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.484
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.818
Given I shutdown Tails and wait for the computer to power off 6.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.485
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.271
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.059
And Tor is ready 16.245
Then the Upgrader considers the system as up-to-date 0.354
# 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.145
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.890
After features/support/hooks.rb:315 0.667
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.187
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.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 1.167
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 20.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.423
After features/support/hooks.rb:315 0.944
After features/support/hooks.rb:100 0.000