Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 29 13 Nov 2024, 07:13

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 20:55.755 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:49.262
Before features/support/hooks.rb:269 0.006
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 32.840
When I start Tails from USB drive "old" with network unplugged 2:10.035
Then the boot device has safe access rights 3.664
And Tails is running from USB drive "old" 0.470
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.390
And I unplug USB drive "old" 0.276
After features/support/hooks.rb:326 3.925
After features/support/hooks.rb:100 0.012
Tags: @product
2:20.219
Before features/support/hooks.rb:269 0.008
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login 1:33.467
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 33.693
And I take note of which tps features are available 1.799
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 9.734
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.011
Tags: @product
3:20.217
Before features/support/hooks.rb:269 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.994
Then Tails is running from USB drive "old" 0.399
And all tps features are active 2.154
When I write some files expected to persist 5.955
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.631
And I take note of which tps features are available 0.541
And I shutdown Tails and wait for the computer to power off 4.164
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.429
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.013
Tags: @product
2:41.972
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.418
And I log in to a new session 24.131
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.991
And I plug USB drive "to_upgrade" 2.688
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.098
Then the running Tails is installed on USB drive "to_upgrade" 23.135
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 7.704
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.166
Before features/support/hooks.rb:269 0.022
Given a computer 0.713
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.515
Then all tps features from the old Tails version are active 3.290
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.444
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.370
After features/support/hooks.rb:326 0.828
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.887
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 13.643
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.084
And Tor is ready 21.355
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.720
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.594
Given I shutdown Tails and wait for the computer to power off 14.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.623
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 3.011
And the file system changes introduced in version 6.2~testoverlayfs are present 0.581
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.489
When the network is plugged 0.122
And Tor is ready 18.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.056
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.839
Given I shutdown Tails and wait for the computer to power off 6.618
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.742
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.393
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.065
And Tor is ready 18.202
Then the Upgrader considers the system as up-to-date 0.323
# 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 16.814
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.114
After features/support/hooks.rb:326 0.930
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.031
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 10.562
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.701
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.801
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 16.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.978
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.000