Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 16 02 Nov 2024, 06:49

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:16.955 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.415
Before features/support/hooks.rb:269 0.003
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 29.342
When I start Tails from USB drive "old" with network unplugged 1:20.956
Then the boot device has safe access rights 2.886
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 6.905
After features/support/hooks.rb:100 0.006
Tags: @product
2:3.755
Before features/support/hooks.rb:269 0.002
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login 1:21.564
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 30.885
And I take note of which tps features are available 1.431
Then a Tails persistence partition exists on USB drive "old" 0.724
And I shutdown Tails and wait for the computer to power off 8.680
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.006
Tags: @product
2:48.121
Before features/support/hooks.rb:269 0.002
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.812
Then Tails is running from USB drive "old" 0.433
And all tps features are active 1.937
When I write some files expected to persist 1.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.435
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 4.513
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.765
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.005
Tags: @product
2:27.814
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.924
And I log in to a new session 19.069
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.621
And I plug USB drive "to_upgrade" 4.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.278
Then the running Tails is installed on USB drive "to_upgrade" 19.307
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 7.743
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.971
Before features/support/hooks.rb:269 0.003
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.771
Then all tps features from the old Tails version are active 1.597
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 2.729
And the expected persistent files created with the old Tails version are present in the filesystem 1.281
And all persistent directories from the old Tails version have safe access rights 2.142
After features/support/hooks.rb:326 1.035
After features/support/hooks.rb:100 0.006
6:24.372
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.183
And no SquashFS delta is installed 0.277
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.070
And Tor is ready 48.397
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.199
Given I shutdown Tails and wait for the computer to power off 8.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.343
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.389
# 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.523
When the network is plugged 0.066
And Tor is ready 16.007
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.281
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.951
Given I shutdown Tails and wait for the computer to power off 4.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.170
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.454
When the network is plugged 0.075
And Tor is ready 20.907
Then the Upgrader considers the system as up-to-date 0.307
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.309
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.012
35.503
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 9.648
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.919
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.415
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.062
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000