Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 61 10 Dec 2024, 22:45

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:14.960 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:13.502
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.914
When I start Tails from USB drive "old" with network unplugged 1:36.924
Then the boot device has safe access rights 3.257
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.321
After features/support/hooks.rb:326 4.182
After features/support/hooks.rb:100 0.067
Tags: @product
2:16.177
Before features/support/hooks.rb:269 0.040
Given a computer 0.478
And I start Tails from USB drive "old" with network unplugged and I login 1:31.455
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 32.859
And I take note of which tps features are available 1.563
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.555
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.804
Before features/support/hooks.rb:269 0.006
Given a computer 0.368
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.894
Then Tails is running from USB drive "old" 1.701
And all tps features are active 2.428
When I write some files expected to persist 3.103
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.628
And I take note of which tps features are available 0.680
And I shutdown Tails and wait for the computer to power off 6.960
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.368
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.213
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 12.406
And I log in to a new session 22.457
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.771
And I plug USB drive "to_upgrade" 5.015
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.531
Then the running Tails is installed on USB drive "to_upgrade" 23.544
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 7.233
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.422
Before features/support/hooks.rb:269 0.008
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.391
Then all tps features from the old Tails version are active 1.897
And Tails is running from USB drive "to_upgrade" 0.425
And the boot device has safe access rights 3.649
And the expected persistent files created with the old Tails version are present in the filesystem 1.794
And all persistent directories from the old Tails version have safe access rights 3.048
After features/support/hooks.rb:326 1.291
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:56.072
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 16.441
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.076
And Tor is ready 23.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.999
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.069
Given I shutdown Tails and wait for the computer to power off 11.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.153
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.318
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.312
When the network is plugged 0.082
And Tor is ready 16.638
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.023
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.785
Given I shutdown Tails and wait for the computer to power off 6.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.604
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.831
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.643
When the network is plugged 0.069
And Tor is ready 18.008
Then the Upgrader considers the system as up-to-date 10.905
# 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 18.088
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.255
After features/support/hooks.rb:326 0.876
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
41.767
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.940
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 23.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.828
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.000