Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 69 15 Dec 2024, 07: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 18:41.958 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:6.839
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.499
When I start Tails from USB drive "old" with network unplugged 1:32.065
Then the boot device has safe access rights 2.963
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.720
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.856
Before features/support/hooks.rb:269 0.004
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:21.356
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 31.445
And I take note of which tps features are available 1.344
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 6.349
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.013
Tags: @product
3:0.526
Before features/support/hooks.rb:269 0.007
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.930
Then Tails is running from USB drive "old" 0.343
And all tps features are active 2.103
When I write some files expected to persist 1.955
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.423
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.165
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.276
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.136
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.960
And I log in to a new session 23.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.587
And I plug USB drive "to_upgrade" 3.811
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.014
Then the running Tails is installed on USB drive "to_upgrade" 22.283
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 2.594
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.130
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.820
Then all tps features from the old Tails version are active 1.656
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.043
And the expected persistent files created with the old Tails version are present in the filesystem 1.340
And all persistent directories from the old Tails version have safe access rights 2.738
After features/support/hooks.rb:326 1.686
After features/support/hooks.rb:100 0.008
6:17.566
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.051
And no SquashFS delta is installed 0.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.178
And Tor is ready 21.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.410
Given I shutdown Tails and wait for the computer to power off 8.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.804
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.259
When the network is plugged 0.078
And Tor is ready 18.849
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.883
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.851
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.825
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.036
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.074
And Tor is ready 19.286
Then the Upgrader considers the system as up-to-date 0.305
# 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.939
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.007
After features/support/hooks.rb:326 1.000
After features/support/hooks.rb:100 0.017
34.903
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.951
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.824
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 18.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.890
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.000