Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 15 22 Nov 2024, 10:34

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:16.186 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.089
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.132
And I write an old version of the Tails USB image to disk "old" 33.234
When I start Tails from USB drive "old" with network unplugged 1:35.311
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.696
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:24.982
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 33.304
And I take note of which tps features are available 1.538
Then a Tails persistence partition exists on USB drive "old" 0.906
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.993
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.935
Then Tails is running from USB drive "old" 1.193
And all tps features are active 2.375
When I write some files expected to persist 1.681
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 3.778
And I take note of which tps features are available 2.105
And I shutdown Tails and wait for the computer to power off 4.326
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.771
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
3:11.824
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 48.195
And I log in to a new session 19.586
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.017
And I plug USB drive "to_upgrade" 2.560
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.897
Then the running Tails is installed on USB drive "to_upgrade" 24.145
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.070
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.286
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.605
Then all tps features from the old Tails version are active 1.643
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.422
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.510
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:51.274
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 12.165
And no SquashFS delta is installed 0.672
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.081
And Tor is ready 20.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.810
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.024
Given I shutdown Tails and wait for the computer to power off 15.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.074
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.275
And the file system changes introduced in version 6.2~testoverlayfs are present 0.438
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.313
When the network is plugged 0.075
And Tor is ready 14.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.866
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.188
Given I shutdown Tails and wait for the computer to power off 4.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.291
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.040
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.392
When the network is plugged 0.185
And Tor is ready 16.305
Then the Upgrader considers the system as up-to-date 0.391
# 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 16.119
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.099
After features/support/hooks.rb:326 1.426
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.020
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 10.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.821
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.315
And the signing key used by the Upgrader is outdated 1.571
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 18.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.285
After features/support/hooks.rb:326 0.858
After features/support/hooks.rb:100 0.000