Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 20 27 Nov 2024, 10:35

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.487 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:31.796
Before features/support/hooks.rb:269 0.006
Given a computer 0.432
And I create a 7200 MiB disk named "old" 0.325
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 34.490
When I start Tails from USB drive "old" with network unplugged 1:51.322
Then the boot device has safe access rights 3.091
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:326 7.441
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.492
Before features/support/hooks.rb:269 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:28.771
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 31.411
And I take note of which tps features are available 2.118
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.731
After features/support/hooks.rb:326 0.332
After features/support/hooks.rb:100 0.013
Tags: @product
3:4.792
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.705
Then Tails is running from USB drive "old" 0.445
And all tps features are active 3.985
When I write some files expected to persist 2.048
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.553
And I shutdown Tails and wait for the computer to power off 4.638
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.990
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.046
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.737
And I log in to a new session 21.595
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.769
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.028
Then the running Tails is installed on USB drive "to_upgrade" 25.967
And I unplug USB drive "to_upgrade" 0.310
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:326 3.618
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.535
Before features/support/hooks.rb:269 0.008
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.675
Then all tps features from the old Tails version are active 1.672
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 4.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 2.578
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.061
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.814
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.519
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.171
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.118
And Tor is ready 20.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.665
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.945
Given I shutdown Tails and wait for the computer to power off 10.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.696
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 5.692
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.388
# 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.390
When the network is plugged 0.067
And Tor is ready 14.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.782
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.363
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.159
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.007
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.393
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.089
And Tor is ready 14.536
Then the Upgrader considers the system as up-to-date 10.927
# 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.866
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.125
After features/support/hooks.rb:326 1.244
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.760
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 10.887
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.951
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 16.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.924
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.000