Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 22 29 Nov 2024, 10:27

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:33.878 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:32.191
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 40.507
When I start Tails from USB drive "old" with network unplugged 1:46.057
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.709
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.866
Before features/support/hooks.rb:269 0.007
Given a computer 0.421
And I start Tails from USB drive "old" with network unplugged and I login 1:27.771
Then Tails is running from USB drive "old" 0.456
And I create a persistent partition 31.067
And I take note of which tps features are available 1.781
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 8.568
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.917
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.970
Then Tails is running from USB drive "old" 1.193
And all tps features are active 2.118
When I write some files expected to persist 2.347
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.499
And all persistent directories from the old Tails version have safe access rights 4.327
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 4.265
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.176
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.786
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.282
And I log in to a new session 22.896
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.825
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.535
Then the running Tails is installed on USB drive "to_upgrade" 23.387
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.622
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.368
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.562
Then all tps features from the old Tails version are active 1.780
And Tails is running from USB drive "to_upgrade" 0.497
And the boot device has safe access rights 3.343
And the expected persistent files created with the old Tails version are present in the filesystem 2.318
And all persistent directories from the old Tails version have safe access rights 2.668
After features/support/hooks.rb:326 1.016
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:57.747
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.267
And no SquashFS delta is installed 0.729
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.494
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.378
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.625
When the network is plugged 0.094
And Tor is ready 19.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.178
Given I shutdown Tails and wait for the computer to power off 15.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.460
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.260
When the network is plugged 0.094
And Tor is ready 14.866
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.339
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.854
Given I shutdown Tails and wait for the computer to power off 4.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.934
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.359
And the file system changes introduced in version 6.3~testoverlayfs are present 0.630
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.428
When the network is plugged 0.074
And Tor is ready 14.874
Then the Upgrader considers the system as up-to-date 0.370
# 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.416
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.086
After features/support/hooks.rb:326 1.110
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.001
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 12.909
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.939
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.158
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 19.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.712
After features/support/hooks.rb:326 1.149
After features/support/hooks.rb:100 0.000