Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 40 21 Nov 2024, 07:24

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:53.787 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:23.689
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.691
When I start Tails from USB drive "old" with network unplugged 1:47.486
Then the boot device has safe access rights 3.167
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 7.159
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.984
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:21.615
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 32.069
And I take note of which tps features are available 1.421
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.550
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.683
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.582
Then Tails is running from USB drive "old" 1.178
And all tps features are active 1.947
When I write some files expected to persist 2.521
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.941
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 3.088
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.274
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.101
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.563
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 10.884
And I log in to a new session 21.804
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.517
And I plug USB drive "to_upgrade" 4.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.774
Then the running Tails is installed on USB drive "to_upgrade" 21.669
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.910
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.645
Then all tps features from the old Tails version are active 1.662
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.165
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.536
After features/support/hooks.rb:326 1.007
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:22.143
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.075
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.074
And Tor is ready 20.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.557
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.761
Given I shutdown Tails and wait for the computer to power off 8.628
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.697
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.214
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.288
When the network is plugged 0.081
And Tor is ready 20.781
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.430
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.922
Given I shutdown Tails and wait for the computer to power off 6.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.815
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.473
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.372
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.454
When the network is plugged 0.069
And Tor is ready 19.013
Then the Upgrader considers the system as up-to-date 0.304
# 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.483
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.800
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.812
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 12.565
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.055
And the signing key used by the Upgrader is outdated 0.767
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 17.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.538
After features/support/hooks.rb:326 0.979
After features/support/hooks.rb:100 0.000