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

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 18:35.903 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:6.095
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.822
When I start Tails from USB drive "old" with network unplugged 1:28.031
Then the boot device has safe access rights 2.983
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.484
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.342
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:24.349
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.665
And I take note of which tps features are available 1.676
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.319
After features/support/hooks.rb:326 0.246
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.287
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.578
Then Tails is running from USB drive "old" 0.376
And all tps features are active 1.926
When I write some files expected to persist 1.641
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.228
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.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.043
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.961
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.589
And I log in to a new session 22.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.800
And I plug USB drive "to_upgrade" 4.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.980
Then the running Tails is installed on USB drive "to_upgrade" 21.007
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.058
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.381
Before features/support/hooks.rb:269 0.005
Given a computer 0.262
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.273
Then all tps features from the old Tails version are active 1.625
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.058
And the expected persistent files created with the old Tails version are present in the filesystem 1.512
And all persistent directories from the old Tails version have safe access rights 2.339
After features/support/hooks.rb:326 1.384
After features/support/hooks.rb:100 0.009
6:17.464
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 12.125
And no SquashFS delta is installed 0.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.083
And Tor is ready 20.879
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.264
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.752
Given I shutdown Tails and wait for the computer to power off 8.998
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.967
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.287
When the network is plugged 0.065
And Tor is ready 18.751
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.152
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.935
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.854
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.633
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.461
When the network is plugged 0.062
And Tor is ready 17.098
Then the Upgrader considers the system as up-to-date 10.829
# 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.775
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.943
After features/support/hooks.rb:326 0.915
After features/support/hooks.rb:100 0.017
35.370
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.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.825
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.340
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.000