Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 34 16 Nov 2024, 14:54

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:51.306 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:26.415
Before features/support/hooks.rb:269 0.006
Given a computer 0.512
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 33.550
When I start Tails from USB drive "old" with network unplugged 1:45.913
Then the boot device has safe access rights 4.122
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.170
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:326 7.361
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.209
Before features/support/hooks.rb:269 0.006
Given a computer 0.800
And I start Tails from USB drive "old" with network unplugged and I login 1:32.316
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 35.402
And I take note of which tps features are available 1.979
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.498
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.906
Before features/support/hooks.rb:269 0.004
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.975
Then Tails is running from USB drive "old" 0.847
And all tps features are active 6.443
When I write some files expected to persist 3.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.545
And I take note of which tps features are available 0.721
And I shutdown Tails and wait for the computer to power off 4.688
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.418
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.198
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 37.540
And I log in to a new session 23.265
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.948
And I plug USB drive "to_upgrade" 5.857
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.431
Then the running Tails is installed on USB drive "to_upgrade" 21.714
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 3.875
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.696
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.466
Then all tps features from the old Tails version are active 3.843
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.555
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.775
After features/support/hooks.rb:326 1.470
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:3.227
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 14.306
And no SquashFS delta is installed 0.340
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
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.474
When the network is plugged 0.079
And Tor is ready 24.195
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.716
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.348
Given I shutdown Tails and wait for the computer to power off 14.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.381
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.968
And the file system changes introduced in version 6.2~testoverlayfs are present 0.630
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.432
# 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.481
When the network is plugged 0.084
And Tor is ready 19.336
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.706
Given I shutdown Tails and wait for the computer to power off 8.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.832
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.515
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.369
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.433
When the network is plugged 0.077
And Tor is ready 19.581
Then the Upgrader considers the system as up-to-date 10.890
# 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 17.381
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.069
After features/support/hooks.rb:326 0.719
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.652
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.515
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.593
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.801
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 19.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.702
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.000