Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 25 02 Dec 2024, 10:16

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:54.631 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:8.331
Before features/support/hooks.rb:269 0.004
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.823
When I start Tails from USB drive "old" with network unplugged 1:34.262
Then the boot device has safe access rights 2.955
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.716
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.430
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:29.352
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 28.838
And I take note of which tps features are available 1.696
Then a Tails persistence partition exists on USB drive "old" 0.740
And I shutdown Tails and wait for the computer to power off 8.307
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.645
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.728
Then Tails is running from USB drive "old" 0.396
And all tps features are active 1.962
When I write some files expected to persist 1.656
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.577
And I take note of which tps features are available 1.041
And I shutdown Tails and wait for the computer to power off 4.583
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.921
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.006
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.377
And I log in to a new session 19.095
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.560
And I plug USB drive "to_upgrade" 2.362
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.022
Then the running Tails is installed on USB drive "to_upgrade" 24.180
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 7.043
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.298
Before features/support/hooks.rb:269 0.004
Given a computer 0.382
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.374
Then all tps features from the old Tails version are active 1.479
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.214
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.261
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:8.176
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 12.435
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.272
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.065
And Tor is ready 18.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.942
Given I shutdown Tails and wait for the computer to power off 8.630
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.305
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.234
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.291
When the network is plugged 0.067
And Tor is ready 14.561
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.818
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.823
Given I shutdown Tails and wait for the computer to power off 4.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.711
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.068
And Tor is ready 15.757
Then the Upgrader considers the system as up-to-date 0.338
# 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.472
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.928
After features/support/hooks.rb:326 0.925
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
51.743
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 24.642
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.941
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.833
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 18.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.918
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.000