Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 23 07 Nov 2024, 20: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 19:25.085 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:11.958
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.261
When I start Tails from USB drive "old" with network unplugged 1:36.123
Then the boot device has safe access rights 3.247
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 9.793
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.062
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:22.155
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 32.190
And I take note of which tps features are available 3.071
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 6.254
After features/support/hooks.rb:326 0.229
After features/support/hooks.rb:100 0.011
Tags: @product
2:58.662
Before features/support/hooks.rb:269 0.007
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.858
Then Tails is running from USB drive "old" 1.578
And all tps features are active 2.510
When I write some files expected to persist 4.174
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.569
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.534
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.020
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.922
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 11.965
And I log in to a new session 23.093
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.958
And I plug USB drive "to_upgrade" 2.875
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.793
Then the running Tails is installed on USB drive "to_upgrade" 20.800
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.505
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.275
Before features/support/hooks.rb:269 0.008
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.895
Then all tps features from the old Tails version are active 1.729
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.123
And the expected persistent files created with the old Tails version are present in the filesystem 1.416
And all persistent directories from the old Tails version have safe access rights 2.568
After features/support/hooks.rb:326 0.998
After features/support/hooks.rb:100 0.023
6:50.610
Before features/support/hooks.rb:269 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.421
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.074
And Tor is ready 21.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.169
Given I shutdown Tails and wait for the computer to power off 10.793
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.039
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.766
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.420
# 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.395
When the network is plugged 0.072
And Tor is ready 20.437
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.298
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.108
Given I shutdown Tails and wait for the computer to power off 6.586
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.617
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.761
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.070
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.426
When the network is plugged 0.079
And Tor is ready 19.218
Then the Upgrader considers the system as up-to-date 0.306
# 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.754
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.983
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.019
36.592
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 9.835
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.151
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.291
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.000