Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 37 19 Nov 2024, 07:19

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 19:11.841 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:19.213
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 28.712
When I start Tails from USB drive "old" with network unplugged 1:45.067
Then the boot device has safe access rights 3.117
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.523
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.356
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:18.988
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 31.261
And I take note of which tps features are available 1.372
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.314
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.990
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.708
Then Tails is running from USB drive "old" 1.010
And all tps features are active 1.979
When I write some files expected to persist 1.683
# 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.357
And all persistent directories from the old Tails version have safe access rights 2.606
And I take note of which tps features are available 0.743
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.179
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.759
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 11.876
And I log in to a new session 21.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 3.745
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.490
Then the running Tails is installed on USB drive "to_upgrade" 18.740
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.744
After features/support/hooks.rb:326 4.675
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.293
Before features/support/hooks.rb:269 0.005
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.696
Then all tps features from the old Tails version are active 1.780
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.428
And the expected persistent files created with the old Tails version are present in the filesystem 1.339
And all persistent directories from the old Tails version have safe access rights 2.478
After features/support/hooks.rb:326 1.495
After features/support/hooks.rb:100 0.010
6:49.215
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.333
And no SquashFS delta is installed 0.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.123
And Tor is ready 21.695
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.735
Given I shutdown Tails and wait for the computer to power off 10.762
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.241
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.271
And the file system changes introduced in version 6.2~testoverlayfs are present 0.522
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.357
When the network is plugged 0.094
And Tor is ready 47.766
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.616
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.920
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.166
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.585
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.369
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.407
When the network is plugged 0.088
And Tor is ready 21.373
Then the Upgrader considers the system as up-to-date 0.291
# 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.834
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.068
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.019
35.012
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
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.776
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 17.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.365
After features/support/hooks.rb:326 0.642
After features/support/hooks.rb:100 0.000