Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 59 08 Dec 2024, 07:04

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:45.538 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:11.511
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.078
When I start Tails from USB drive "old" with network unplugged 1:34.149
Then the boot device has safe access rights 2.917
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.590
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:29.319
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 32.202
And I take note of which tps features are available 1.444
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 8.192
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.997
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.802
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.036
When I write some files expected to persist 1.600
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.273
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.045
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.255
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.216
And I log in to a new session 22.494
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.505
And I plug USB drive "to_upgrade" 2.859
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.023
Then the running Tails is installed on USB drive "to_upgrade" 21.736
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 3.573
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.635
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.131
Then all tps features from the old Tails version are active 1.782
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.233
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:326 1.023
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:20.388
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 11.580
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.627
When the network is plugged 0.068
And Tor is ready 21.007
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.024
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.527
Given I shutdown Tails and wait for the computer to power off 10.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.707
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.264
When the network is plugged 0.060
And Tor is ready 19.075
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.023
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.351
Given I shutdown Tails and wait for the computer to power off 4.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.896
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.179
And the file system changes introduced in version 6.3~testoverlayfs are present 0.675
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.354
When the network is plugged 0.076
And Tor is ready 17.894
Then the Upgrader considers the system as up-to-date 10.851
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.060
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.159
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 9.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
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.912
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 18.349
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.836
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000