Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 48 26 Nov 2024, 17: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 20:40.933 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:9.424
Before features/support/hooks.rb:269 0.005
Given a computer 0.260
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 37.173
When I start Tails from USB drive "old" with network unplugged 1:26.679
Then the boot device has safe access rights 3.203
And Tails is running from USB drive "old" 0.321
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.292
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 7.289
After features/support/hooks.rb:100 0.012
Tags: @product
2:27.155
Before features/support/hooks.rb:269 0.006
Given a computer 1.155
And I start Tails from USB drive "old" with network unplugged and I login 1:26.537
Then Tails is running from USB drive "old" 0.452
And I create a persistent partition 42.592
And I take note of which tps features are available 6.791
Then a Tails persistence partition exists on USB drive "old" 1.383
And I shutdown Tails and wait for the computer to power off 8.241
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
3:11.260
Before features/support/hooks.rb:269 0.004
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.755
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.678
When I write some files expected to persist 1.910
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.339
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.422
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.007
Tags: @product
2:41.182
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.886
And I log in to a new session 19.053
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.785
And I plug USB drive "to_upgrade" 2.777
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.917
Then the running Tails is installed on USB drive "to_upgrade" 25.267
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.269
After features/support/hooks.rb:326 7.241
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.048
Before features/support/hooks.rb:269 0.005
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.349
Then all tps features from the old Tails version are active 2.020
And Tails is running from USB drive "to_upgrade" 0.426
And the boot device has safe access rights 4.115
And the expected persistent files created with the old Tails version are present in the filesystem 1.887
And all persistent directories from the old Tails version have safe access rights 2.995
After features/support/hooks.rb:326 1.518
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:9.940
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 15.179
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.607
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.152
And Tor is ready 51.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.846
Given I shutdown Tails and wait for the computer to power off 10.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.113
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 4.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.352
When the network is plugged 0.101
And Tor is ready 18.190
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.489
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.168
Given I shutdown Tails and wait for the computer to power off 4.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.316
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.393
And the file system changes introduced in version 6.3~testoverlayfs are present 0.663
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.404
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.330
When the network is plugged 0.068
And Tor is ready 18.220
Then the Upgrader considers the system as up-to-date 0.348
# 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.433
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.116
After features/support/hooks.rb:326 0.798
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.921
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.807
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.557
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 21.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.054
After features/support/hooks.rb:326 0.937
After features/support/hooks.rb:100 0.000