Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 42 23 Nov 2024, 07:26

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 19:39.074 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:7.759
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.706
When I start Tails from USB drive "old" with network unplugged 1:33.748
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 7.666
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.824
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:21.956
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.005
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.726
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.726
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.260
Then Tails is running from USB drive "old" 1.413
And all tps features are active 2.251
When I write some files expected to persist 3.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 3.308
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 4.356
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.503
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.691
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.084
And I log in to a new session 20.430
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.626
And I plug USB drive "to_upgrade" 2.719
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.758
Then the running Tails is installed on USB drive "to_upgrade" 17.637
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.468
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.103
Before features/support/hooks.rb:269 0.005
Given a computer 0.313
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.105
Then all tps features from the old Tails version are active 2.010
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.633
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.289
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:17.147
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.905
And no SquashFS delta is installed 0.493
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.247
When the network is plugged 0.082
And Tor is ready 21.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.991
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.773
Given I shutdown Tails and wait for the computer to power off 1:21.187
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.429
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.494
# 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.249
When the network is plugged 0.062
And Tor is ready 17.110
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.059
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.029
Given I shutdown Tails and wait for the computer to power off 4.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.568
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.074
And Tor is ready 17.293
Then the Upgrader considers the system as up-to-date 0.307
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.980
After features/support/hooks.rb:326 0.967
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.822
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.450
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.537
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.767
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.252
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.675
After features/support/hooks.rb:326 0.653
After features/support/hooks.rb:100 0.000