Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 25 08 Nov 2024, 07:43

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:45.385 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:10.065
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.966
When I start Tails from USB drive "old" with network unplugged 1:34.846
Then the boot device has safe access rights 3.029
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.024
Tags: @product
2:6.297
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:22.210
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 33.096
And I take note of which tps features are available 1.459
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.194
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.836
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.491
Then Tails is running from USB drive "old" 0.592
And all tps features are active 2.036
When I write some files expected to persist 1.765
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.995
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.338
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.283
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.225
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.794
And I log in to a new session 23.040
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.609
And I plug USB drive "to_upgrade" 2.727
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.716
Then the running Tails is installed on USB drive "to_upgrade" 22.916
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.477
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.017
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.341
Then all tps features from the old Tails version are active 1.860
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.113
And the expected persistent files created with the old Tails version are present in the filesystem 1.455
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:326 1.436
After features/support/hooks.rb:100 0.007
6:18.727
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 11.861
And no SquashFS delta is installed 0.257
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.069
And Tor is ready 20.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.484
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.035
Given I shutdown Tails and wait for the computer to power off 8.670
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.522
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.357
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
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.325
# 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.298
When the network is plugged 0.101
And Tor is ready 19.963
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.716
Given I shutdown Tails and wait for the computer to power off 6.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.714
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.375
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.070
And Tor is ready 17.110
Then the Upgrader considers the system as up-to-date 0.299
# 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.777
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.243
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.028
37.215
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 11.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.790
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 18.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.440
After features/support/hooks.rb:326 0.954
After features/support/hooks.rb:100 0.000