Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 26 03 Dec 2024, 10:20

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 19:34.985 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:14.759
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.328
When I start Tails from USB drive "old" with network unplugged 1:39.130
Then the boot device has safe access rights 2.980
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.537
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:22.832
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.271
And I take note of which tps features are available 1.790
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.343
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.185
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.310
Then Tails is running from USB drive "old" 0.376
And all tps features are active 1.964
When I write some files expected to persist 1.888
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.450
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 4.100
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.702
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.212
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.911
And I log in to a new session 21.296
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.420
Then the running Tails is installed on USB drive "to_upgrade" 22.932
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 2.394
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.129
Before features/support/hooks.rb:269 0.008
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.311
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.611
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 2.450
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
6:35.294
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.083
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.402
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.067
And Tor is ready 19.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.093
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.663
Given I shutdown Tails and wait for the computer to power off 8.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.850
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.416
When the network is plugged 0.085
And Tor is ready 14.682
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.688
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.767
Given I shutdown Tails and wait for the computer to power off 4.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.120
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.511
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.081
And Tor is ready 14.957
Then the Upgrader considers the system as up-to-date 10.822
# 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.356
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.056
After features/support/hooks.rb:326 0.936
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
39.867
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.557
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.536
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.851
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 18.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.825
After features/support/hooks.rb:326 1.087
After features/support/hooks.rb:100 0.000