Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 7 14 Nov 2024, 10:34

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:31.506 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:28.329
Before features/support/hooks.rb:269 0.005
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 33.270
When I start Tails from USB drive "old" with network unplugged 1:48.912
Then the boot device has safe access rights 3.680
And Tails is running from USB drive "old" 0.415
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.737
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.066
Before features/support/hooks.rb:269 0.006
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login 1:28.505
Then Tails is running from USB drive "old" 0.802
And I create a persistent partition 35.970
And I take note of which tps features are available 3.970
Then a Tails persistence partition exists on USB drive "old" 1.043
And I shutdown Tails and wait for the computer to power off 8.519
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.307
Before features/support/hooks.rb:269 0.005
Given a computer 1.399
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.349
Then Tails is running from USB drive "old" 0.732
And all tps features are active 2.356
When I write some files expected to persist 2.428
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.415
And I take note of which tps features are available 0.579
And I shutdown Tails and wait for the computer to power off 4.484
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.949
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.007
Tags: @product
2:42.011
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.826
And I log in to a new session 21.114
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.807
And I plug USB drive "to_upgrade" 3.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.077
Then the running Tails is installed on USB drive "to_upgrade" 26.336
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.448
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.140
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.567
Then all tps features from the old Tails version are active 2.256
And Tails is running from USB drive "to_upgrade" 0.549
And the boot device has safe access rights 4.056
And the expected persistent files created with the old Tails version are present in the filesystem 1.729
And all persistent directories from the old Tails version have safe access rights 2.777
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:46.627
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 13.640
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.629
When the network is plugged 0.089
And Tor is ready 20.730
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.721
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.060
Given I shutdown Tails and wait for the computer to power off 11.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.936
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.555
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.358
When the network is plugged 0.094
And Tor is ready 16.063
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.758
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.255
Given I shutdown Tails and wait for the computer to power off 4.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.579
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.357
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.067
And Tor is ready 14.670
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 15.663
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.274
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
35.024
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 10.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 1.339
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 17.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.545
After features/support/hooks.rb:326 1.249
After features/support/hooks.rb:100 0.000