Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 24 01 Dec 2024, 10:12

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:49.870 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.398
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.182
When I start Tails from USB drive "old" with network unplugged 1:34.692
Then the boot device has safe access rights 3.111
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.286
After features/support/hooks.rb:326 3.520
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.363
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:25.287
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 30.229
And I take note of which tps features are available 1.402
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.139
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.859
Before features/support/hooks.rb:269 0.006
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.062
Then Tails is running from USB drive "old" 1.340
And all tps features are active 2.243
When I write some files expected to persist 1.701
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 3.502
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.646
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.039
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.773
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.736
And I log in to a new session 25.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.937
Then the running Tails is installed on USB drive "to_upgrade" 22.369
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.369
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:5.109
Then all tps features from the old Tails version are active 1.643
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.087
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 3.607
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:16.028
Before features/support/hooks.rb:269 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.959
And no SquashFS delta is installed 0.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.837
When the network is plugged 0.061
And Tor is ready 20.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.324
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.081
Given I shutdown Tails and wait for the computer to power off 10.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.742
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.473
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.129
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.423
When the network is plugged 0.075
And Tor is ready 15.624
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.719
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.082
Given I shutdown Tails and wait for the computer to power off 4.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.697
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.337
When the network is plugged 0.078
And Tor is ready 14.711
Then the Upgrader considers the system as up-to-date 0.315
# 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.013
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.968
After features/support/hooks.rb:326 1.019
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.075
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.393
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.879
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 21.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.098
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.000