Project Number Date
test_Tails_ISO_20522-ocr-more 5 15 Dec 2024, 05:17

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 18:57.250 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
1:57.710
Before features/support/hooks.rb:269 0.004
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.605
When I start Tails from USB drive "old" with network unplugged 1:22.861
Then the boot device has safe access rights 2.987
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 7.014
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.131
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:29.870
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 33.391
And I take note of which tps features are available 1.455
Then a Tails persistence partition exists on USB drive "old" 0.734
And I shutdown Tails and wait for the computer to power off 8.204
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.259
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.268
Then Tails is running from USB drive "old" 0.474
And all tps features are active 1.874
When I write some files expected to persist 1.865
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.288
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.260
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.963
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.986
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.520
And I log in to a new session 23.416
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.708
And I plug USB drive "to_upgrade" 2.766
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.908
Then the running Tails is installed on USB drive "to_upgrade" 22.239
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.670
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.822
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.636
Then all tps features from the old Tails version are active 1.878
And Tails is running from USB drive "to_upgrade" 0.556
And the boot device has safe access rights 3.253
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.777
After features/support/hooks.rb:326 1.417
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:40.555
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.952
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.472
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.073
And Tor is ready 23.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.248
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.813
Given I shutdown Tails and wait for the computer to power off 8.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.357
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.364
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.579
# 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.257
When the network is plugged 0.094
And Tor is ready 18.666
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.936
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.893
Given I shutdown Tails and wait for the computer to power off 4.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.849
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.448
When the network is plugged 0.070
And Tor is ready 48.720
Then the Upgrader considers the system as up-to-date 0.305
# 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.741
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:326 0.755
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
33.785
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 10.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.948
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.032
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000