Project Number Date
test_Tails_ISO_stable 4876 06 Jun 2024, 12:22

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:59.543 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:0.236
Before features/support/hooks.rb:269 0.007
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.322
When I start Tails from USB drive "old" with network unplugged 1:24.738
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:315 3.487
After features/support/hooks.rb:100 0.060
Tags: @product
2:11.829
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:24.481
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 36.071
And I take note of which tps features are available 1.391
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.477
After features/support/hooks.rb:315 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.539
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.527
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.825
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.379
And I take note of which tps features are available 0.379
And I shutdown Tails and wait for the computer to power off 4.047
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.353
After features/support/hooks.rb:315 0.127
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.521
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.815
And I log in to a new session 17.313
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 2.459
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.974
Then the running Tails is installed on USB drive "to_upgrade" 16.917
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:315 2.044
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.811
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.617
Then all tps features from the old Tails version are active 1.556
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.026
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.710
After features/support/hooks.rb:315 0.883
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:55.854
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 12.106
And no SquashFS delta is installed 0.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.036
And Tor is ready 27.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.638
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.526
Given I shutdown Tails and wait for the computer to power off 1:22.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.722
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.276
When the network is plugged 0.065
And Tor is ready 20.880
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.861
Given I shutdown Tails and wait for the computer to power off 4.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.595
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.264
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.039
And Tor is ready 16.164
Then the Upgrader considers the system as up-to-date 0.385
# 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.994
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.961
After features/support/hooks.rb:315 0.784
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
36.751
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 1.398
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 17.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.732
After features/support/hooks.rb:315 1.988
After features/support/hooks.rb:100 0.000