Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 8 15 Nov 2024, 10:31

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 20:23.137 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:16.550
Before features/support/hooks.rb:269 0.006
Given a computer 0.232
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.829
When I start Tails from USB drive "old" with network unplugged 1:39.926
Then the boot device has safe access rights 3.403
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.536
After features/support/hooks.rb:100 0.011
Tags: @product
2:19.980
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:36.027
Then Tails is running from USB drive "old" 0.432
And I create a persistent partition 32.509
And I take note of which tps features are available 1.568
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 8.333
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.011
Tags: @product
3:7.619
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.710
Then Tails is running from USB drive "old" 0.452
And all tps features are active 2.721
When I write some files expected to persist 2.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.556
And all persistent directories from the old Tails version have safe access rights 2.661
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.843
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.935
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 11.754
And I log in to a new session 19.103
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.590
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.875
Then the running Tails is installed on USB drive "to_upgrade" 24.709
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.522
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.507
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.811
Then all tps features from the old Tails version are active 2.172
And Tails is running from USB drive "to_upgrade" 0.402
And the boot device has safe access rights 3.626
And the expected persistent files created with the old Tails version are present in the filesystem 1.655
And all persistent directories from the old Tails version have safe access rights 2.642
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:55.869
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 18.107
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.091
And Tor is ready 20.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.057
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.723
Given I shutdown Tails and wait for the computer to power off 10.998
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.066
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.556
And the file system changes introduced in version 6.2~testoverlayfs are present 0.409
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.365
# 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.368
When the network is plugged 0.079
And Tor is ready 15.006
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.688
Given I shutdown Tails and wait for the computer to power off 6.799
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.915
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.577
And the file system changes introduced in version 6.3~testoverlayfs are present 0.570
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.452
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.074
And Tor is ready 14.549
Then the Upgrader considers the system as up-to-date 0.397
# 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.102
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.215
After features/support/hooks.rb:326 1.233
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.674
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 13.452
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.521
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.816
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 16.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.238
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.000