Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 60 09 Dec 2024, 07:06

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:32.231 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:30.048
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 30.609
When I start Tails from USB drive "old" with network unplugged 1:53.137
Then the boot device has safe access rights 3.727
And Tails is running from USB drive "old" 0.429
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:326 3.645
After features/support/hooks.rb:100 0.014
Tags: @product
2:25.458
Before features/support/hooks.rb:269 0.010
Given a computer 0.512
And I start Tails from USB drive "old" with network unplugged and I login 1:41.348
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 32.429
And I take note of which tps features are available 1.551
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 8.347
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.854
Before features/support/hooks.rb:269 0.007
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.351
Then Tails is running from USB drive "old" 1.728
And all tps features are active 2.101
When I write some files expected to persist 3.270
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.415
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.442
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.098
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.986
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.533
And I log in to a new session 22.155
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.539
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.636
Then the running Tails is installed on USB drive "to_upgrade" 20.857
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.618
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.865
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.816
Then all tps features from the old Tails version are active 2.078
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.239
And the expected persistent files created with the old Tails version are present in the filesystem 1.608
And all persistent directories from the old Tails version have safe access rights 2.526
After features/support/hooks.rb:326 1.479
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:15.620
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 31.894
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.083
And Tor is ready 22.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.261
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.939
Given I shutdown Tails and wait for the computer to power off 11.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.329
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.418
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.458
When the network is plugged 0.072
And Tor is ready 18.423
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.914
Given I shutdown Tails and wait for the computer to power off 4.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.436
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.330
And the file system changes introduced in version 6.3~testoverlayfs are present 0.619
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.082
And Tor is ready 48.185
Then the Upgrader considers the system as up-to-date 0.329
# 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.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.228
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.398
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 11.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.929
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 19.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.443
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.000