Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 47 26 Nov 2024, 16:37

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:26.880 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.733
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.070
When I start Tails from USB drive "old" with network unplugged 1:32.979
Then the boot device has safe access rights 3.386
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.559
After features/support/hooks.rb:100 0.021
Tags: @product
2:10.928
Before features/support/hooks.rb:269 0.009
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:26.956
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 32.387
And I take note of which tps features are available 1.470
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.741
After features/support/hooks.rb:326 0.222
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.061
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.483
Then Tails is running from USB drive "old" 1.488
And all tps features are active 2.038
When I write some files expected to persist 3.129
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.665
And all persistent directories from the old Tails version have safe access rights 3.709
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.239
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.395
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.790
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.745
And I log in to a new session 28.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.337
And I plug USB drive "to_upgrade" 2.757
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.778
Then the running Tails is installed on USB drive "to_upgrade" 21.137
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:326 7.228
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.336
Before features/support/hooks.rb:269 0.007
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.792
Then all tps features from the old Tails version are active 1.801
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.414
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:326 0.865
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:38.526
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.960
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.574
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.355
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.071
And Tor is ready 21.490
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.135
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.375
Given I shutdown Tails and wait for the computer to power off 11.135
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.436
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.520
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.332
When the network is plugged 0.081
And Tor is ready 20.462
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.928
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.993
Given I shutdown Tails and wait for the computer to power off 4.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.385
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 4.321
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.381
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.065
And Tor is ready 18.363
Then the Upgrader considers the system as up-to-date 0.309
# 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 14.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.984
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
37.503
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 10.885
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.989
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.080
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.063
After features/support/hooks.rb:326 0.887
After features/support/hooks.rb:100 0.000