Project Number Date
test_Tails_ISO_stable 5216 24 Oct 2024, 08:42

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:48.967 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:25.123
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.896
When I start Tails from USB drive "old" with network unplugged 1:46.740
Then the boot device has safe access rights 3.136
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 3.810
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.124
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:20.826
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 32.441
And I take note of which tps features are available 1.284
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 6.298
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.011
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.491
Then Tails is running from USB drive "old" 0.931
And all tps features are active 2.041
When I write some files expected to persist 2.915
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.326
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.778
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.397
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.786
And I log in to a new session 22.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.464
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.824
Then the running Tails is installed on USB drive "to_upgrade" 22.787
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.345
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.487
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.156
Then all tps features from the old Tails version are active 1.695
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.046
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.559
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:55.991
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 13.190
And no SquashFS delta is installed 0.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.080
And Tor is ready 23.684
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.260
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.605
Given I shutdown Tails and wait for the computer to power off 10.876
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.979
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.385
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.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.324
When the network is plugged 0.074
And Tor is ready 18.978
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.384
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.191
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.042
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.403
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.275
When the network is plugged 0.072
And Tor is ready 48.401
Then the Upgrader considers the system as up-to-date 0.302
# 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.004
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.008
After features/support/hooks.rb:326 0.699
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
42.833
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 16.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.821
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.466
After features/support/hooks.rb:326 0.611
After features/support/hooks.rb:100 0.000