Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 4 27 Oct 2024, 06:36

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 17:51.756 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
1:55.936
Before features/support/hooks.rb:269 0.003
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 29.046
When I start Tails from USB drive "old" with network unplugged 1:21.840
Then the boot device has safe access rights 2.863
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 3.548
After features/support/hooks.rb:100 0.006
Tags: @product
1:59.731
Before features/support/hooks.rb:269 0.003
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:19.446
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 30.985
And I take note of which tps features are available 1.617
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 6.470
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.006
Tags: @product
2:43.624
Before features/support/hooks.rb:269 0.003
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.127
Then Tails is running from USB drive "old" 0.513
And all tps features are active 2.001
When I write some files expected to persist 1.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.827
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.224
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.120
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.006
Tags: @product
2:29.560
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.912
And I log in to a new session 20.366
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.667
And I plug USB drive "to_upgrade" 2.993
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.715
Then the running Tails is installed on USB drive "to_upgrade" 20.493
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 2.873
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.551
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:54.539
Then all tps features from the old Tails version are active 1.550
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.324
And the expected persistent files created with the old Tails version are present in the filesystem 1.351
And all persistent directories from the old Tails version have safe access rights 2.283
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.006
6:6.146
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 11.396
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.084
And Tor is ready 21.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.760
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.394
Given I shutdown Tails and wait for the computer to power off 8.874
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.708
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.438
And only the 6.2~testoverlayfs SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.442
# 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.305
When the network is plugged 0.074
And Tor is ready 16.861
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.401
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.678
Given I shutdown Tails and wait for the computer to power off 4.586
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.941
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.072
And Tor is ready 18.011
Then the Upgrader considers the system as up-to-date 0.299
# 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 14.969
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.020
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.012
33.205
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.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.795
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 16.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.938
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000