Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 70 16 Dec 2024, 07:21

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:15.676 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:19.609
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.268
When I start Tails from USB drive "old" with network unplugged 1:43.951
Then the boot device has safe access rights 3.012
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.545
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.963
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:24.034
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 30.327
And I take note of which tps features are available 1.877
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.415
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.993
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.086
Then Tails is running from USB drive "old" 0.515
And all tps features are active 2.091
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.440
And I take note of which tps features are available 0.495
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.268
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.843
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.684
And I log in to a new session 23.475
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.661
And I plug USB drive "to_upgrade" 3.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.826
Then the running Tails is installed on USB drive "to_upgrade" 20.542
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.524
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.057
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.247
Then all tps features from the old Tails version are active 1.895
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.569
And the expected persistent files created with the old Tails version are present in the filesystem 1.350
And all persistent directories from the old Tails version have safe access rights 2.485
After features/support/hooks.rb:326 1.664
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:24.177
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 12.252
And no SquashFS delta is installed 0.645
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.134
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.637
When the network is plugged 0.077
And Tor is ready 24.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.537
Given I shutdown Tails and wait for the computer to power off 8.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.160
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.480
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.289
When the network is plugged 0.065
And Tor is ready 18.190
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.261
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.572
Given I shutdown Tails and wait for the computer to power off 4.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.440
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.032
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.101
And Tor is ready 19.007
Then the Upgrader considers the system as up-to-date 0.334
# 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 17.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.131
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.031
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.477
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.645
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.833
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.594
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.000