Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 3 09 Nov 2024, 10:19

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:6.385 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:23.864
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.552
When I start Tails from USB drive "old" with network unplugged 1:46.505
Then the boot device has safe access rights 3.424
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:326 3.772
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.955
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:25.751
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 38.938
And I take note of which tps features are available 2.722
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 8.995
After features/support/hooks.rb:326 0.208
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.362
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:19.578
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.427
When I write some files expected to persist 2.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.718
And I take note of which tps features are available 0.601
And I shutdown Tails and wait for the computer to power off 4.496
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.873
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.695
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 13.621
And I log in to a new session 22.390
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.777
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.203
Then the running Tails is installed on USB drive "to_upgrade" 18.651
And I unplug USB drive "to_upgrade" 0.374
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.814
Before features/support/hooks.rb:269 0.015
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.543
Then all tps features from the old Tails version are active 1.956
And Tails is running from USB drive "to_upgrade" 0.482
And the boot device has safe access rights 3.451
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:326 1.043
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:50.393
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.409
And no SquashFS delta is installed 0.835
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.544
When the network is plugged 0.074
And Tor is ready 21.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.139
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.736
Given I shutdown Tails and wait for the computer to power off 10.910
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.397
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.556
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.275
When the network is plugged 0.083
And Tor is ready 16.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.033
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.257
Given I shutdown Tails and wait for the computer to power off 4.638
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.991
Then Tails is running version 6.3~testoverlayfs 0.191
And all tps features are active 2.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.281
When the network is plugged 0.075
And Tor is ready 16.812
Then the Upgrader considers the system as up-to-date 11.121
# 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.693
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.023
After features/support/hooks.rb:326 1.285
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.299
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.643
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.189
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.839
But a current signing key is available on our website 0.000
When the network is plugged 0.463
And Tor is ready 18.680
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.426
After features/support/hooks.rb:326 1.838
After features/support/hooks.rb:100 0.000