Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 19 26 Nov 2024, 10:39

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:13.544 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:29.647
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.969
When I start Tails from USB drive "old" with network unplugged 1:49.784
Then the boot device has safe access rights 3.487
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.265
After features/support/hooks.rb:326 3.760
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.273
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:27.689
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 31.032
And I take note of which tps features are available 2.288
Then a Tails persistence partition exists on USB drive "old" 1.279
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.013
Tags: @product
2:59.419
Before features/support/hooks.rb:269 0.007
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.843
Then Tails is running from USB drive "old" 0.576
And all tps features are active 2.189
When I write some files expected to persist 2.435
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.602
And I take note of which tps features are available 0.567
And I shutdown Tails and wait for the computer to power off 4.386
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.893
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.811
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 33.134
And I log in to a new session 18.811
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.964
And I plug USB drive "to_upgrade" 2.447
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.648
Then the running Tails is installed on USB drive "to_upgrade" 22.327
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 3.605
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.085
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:8.797
Then all tps features from the old Tails version are active 1.848
And Tails is running from USB drive "to_upgrade" 0.381
And the boot device has safe access rights 3.647
And the expected persistent files created with the old Tails version are present in the filesystem 1.600
And all persistent directories from the old Tails version have safe access rights 2.610
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:42.657
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.097
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.091
And Tor is ready 23.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.047
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.888
Given I shutdown Tails and wait for the computer to power off 16.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.512
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.315
When the network is plugged 0.062
And Tor is ready 16.747
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.403
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.001
Given I shutdown Tails and wait for the computer to power off 4.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.066
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.440
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.079
And Tor is ready 14.325
Then the Upgrader considers the system as up-to-date 0.326
# 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.790
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.173
After features/support/hooks.rb:326 0.804
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.648
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 11.676
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.907
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 16.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.041
After features/support/hooks.rb:326 0.978
After features/support/hooks.rb:100 0.000