Project Number Date
test_Tails_ISO_stable 4854 26 May 2024, 13:05

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:28.521 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:6.822
Before features/support/hooks.rb:259 0.005
Given a computer 0.144
And I create a 7200 MiB disk named "old" 0.110
And I plug USB drive "old" 1.113
And I write an old version of the Tails USB image to disk "old" 30.029
When I start Tails from USB drive "old" with network unplugged 1:31.441
Then the boot device has safe access rights 2.976
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:305 7.140
After features/support/hooks.rb:89 0.010
Tags: @product
2:19.502
Before features/support/hooks.rb:259 0.004
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:31.387
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 36.784
And I take note of which tps features are available 1.379
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 8.524
After features/support/hooks.rb:305 0.144
After features/support/hooks.rb:89 0.007
Tags: @product
2:54.060
Before features/support/hooks.rb:259 0.004
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.828
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.215
When I write some files expected to persist 1.786
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.678
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.626
After features/support/hooks.rb:305 0.134
After features/support/hooks.rb:89 0.007
Tags: @product
2:43.552
Before features/support/hooks.rb:259 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 24.890
And I log in to a new session 17.264
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.835
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.018
Then the running Tails is installed on USB drive "to_upgrade" 21.639
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:305 1.860
After features/support/hooks.rb:89 0.000
Tags: @product
2:10.411
Before features/support/hooks.rb:259 0.004
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.997
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.436
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.412
After features/support/hooks.rb:305 0.826
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:25.748
Before features/support/hooks.rb:259 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.326
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.043
And Tor is ready 20.523
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.126
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.854
Given I shutdown Tails and wait for the computer to power off 8.733
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.052
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.273
When the network is plugged 0.032
And Tor is ready 19.789
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.195
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.550
Given I shutdown Tails and wait for the computer to power off 4.468
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.312
Then Tails is running version 6.3~testoverlayfs 0.048
And all tps features are active 1.838
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.028
And Tor is ready 20.726
Then the Upgrader considers the system as up-to-date 0.308
# 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.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:305 0.748
After features/support/hooks.rb:89 0.014
Tags: @product @automatic_upgrade
48.424
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.837
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.483
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 18.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.574
After features/support/hooks.rb:305 0.716
After features/support/hooks.rb:89 0.000