Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 6 29 Oct 2024, 06:46

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:31.651 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:15.220
Before features/support/hooks.rb:269 0.003
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 29.124
When I start Tails from USB drive "old" with network unplugged 1:40.849
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 3.507
After features/support/hooks.rb:100 0.049
Tags: @product
2:7.530
Before features/support/hooks.rb:269 0.002
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:24.150
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 32.077
And I take note of which tps features are available 1.508
Then a Tails persistence partition exists on USB drive "old" 1.016
And I shutdown Tails and wait for the computer to power off 8.307
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.006
Tags: @product
2:51.068
Before features/support/hooks.rb:269 0.003
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.208
Then Tails is running from USB drive "old" 0.361
And all tps features are active 1.975
When I write some files expected to persist 1.807
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.291
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.899
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.006
Tags: @product
2:37.398
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.705
And I log in to a new session 26.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.654
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.611
Then the running Tails is installed on USB drive "to_upgrade" 22.900
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.601
After features/support/hooks.rb:100 0.000
Tags: @product
2:0.010
Before features/support/hooks.rb:269 0.003
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.152
Then all tps features from the old Tails version are active 1.586
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.934
And the expected persistent files created with the old Tails version are present in the filesystem 1.379
And all persistent directories from the old Tails version have safe access rights 2.483
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:7.160
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.159
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.061
And Tor is ready 22.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.823
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.376
Given I shutdown Tails and wait for the computer to power off 8.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.914
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.276
When the network is plugged 0.110
And Tor is ready 18.943
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.064
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.510
Given I shutdown Tails and wait for the computer to power off 4.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.946
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.391
When the network is plugged 0.089
And Tor is ready 17.266
Then the Upgrader considers the system as up-to-date 0.277
# 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 16.016
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.989
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
33.262
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.214
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.764
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 16.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.941
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.000