Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 41 22 Nov 2024, 07:18

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:30.896 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:58.267
Before features/support/hooks.rb:269 0.003
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.901
When I start Tails from USB drive "old" with network unplugged 1:21.938
Then the boot device has safe access rights 3.022
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.430
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:326 7.850
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.462
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:23.314
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.138
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.321
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.353
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.634
Then Tails is running from USB drive "old" 1.510
And all tps features are active 2.223
When I write some files expected to persist 2.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.949
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.996
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.527
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 10.504
And I log in to a new session 21.458
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 3.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.046
Then the running Tails is installed on USB drive "to_upgrade" 23.199
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 7.164
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.428
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.092
Then all tps features from the old Tails version are active 1.649
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.201
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.557
After features/support/hooks.rb:326 0.951
After features/support/hooks.rb:100 0.007
6:19.937
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 11.872
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.514
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.072
And Tor is ready 23.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.088
Given I shutdown Tails and wait for the computer to power off 10.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.028
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.688
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.277
When the network is plugged 0.062
And Tor is ready 17.875
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.809
Given I shutdown Tails and wait for the computer to power off 4.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.462
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.299
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.349
When the network is plugged 0.076
And Tor is ready 17.220
Then the Upgrader considers the system as up-to-date 10.783
# 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.778
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.073
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.013
35.919
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.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.578
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 18.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.271
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.000