Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 45 25 Nov 2024, 16: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 21:52.770 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:20.234
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.010
When I start Tails from USB drive "old" with network unplugged 1:46.614
Then the boot device has safe access rights 3.163
And Tails is running from USB drive "old" 0.426
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 12.187
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.614
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:32.834
Then Tails is running from USB drive "old" 0.435
And I create a persistent partition 32.987
And I take note of which tps features are available 2.001
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.360
After features/support/hooks.rb:326 0.258
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.549
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.366
Then Tails is running from USB drive "old" 1.218
And all tps features are active 2.104
When I write some files expected to persist 1.725
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 4.085
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 4.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.306
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.012
Tags: @product
2:44.835
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.355
And I log in to a new session 23.243
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.869
And I plug USB drive "to_upgrade" 3.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.080
Then the running Tails is installed on USB drive "to_upgrade" 23.629
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.620
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.871
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.124
Then all tps features from the old Tails version are active 2.124
And Tails is running from USB drive "to_upgrade" 0.435
And the boot device has safe access rights 4.276
And the expected persistent files created with the old Tails version are present in the filesystem 1.637
And all persistent directories from the old Tails version have safe access rights 3.077
After features/support/hooks.rb:326 1.603
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:24.747
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 15.788
And no SquashFS delta is installed 0.326
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.594
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.563
When the network is plugged 1.416
And Tor is ready 23.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.574
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.399
Given I shutdown Tails and wait for the computer to power off 1:34.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.320
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.346
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.390
# 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.338
When the network is plugged 0.134
And Tor is ready 20.554
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.512
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.451
Given I shutdown Tails and wait for the computer to power off 4.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.298
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.678
And the file system changes introduced in version 6.3~testoverlayfs are present 0.716
And only the 6.3~testoverlayfs SquashFS delta is installed 0.296
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.538
When the network is plugged 0.095
And Tor is ready 22.275
Then the Upgrader considers the system as up-to-date 0.346
# 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 17.049
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.920
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
37.916
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.742
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 1.067
But a current signing key is available on our website 0.000
When the network is plugged 0.282
And Tor is ready 19.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.574
After features/support/hooks.rb:326 1.384
After features/support/hooks.rb:100 0.000