Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 20 05 Nov 2024, 07:08

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 17:57.365 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:1.604
Before features/support/hooks.rb:269 0.003
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 28.435
When I start Tails from USB drive "old" with network unplugged 1:28.062
Then the boot device has safe access rights 2.870
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.538
After features/support/hooks.rb:100 0.006
Tags: @product
2:0.896
Before features/support/hooks.rb:269 0.002
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:19.579
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 29.968
And I take note of which tps features are available 1.919
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.122
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.006
Tags: @product
2:45.460
Before features/support/hooks.rb:269 0.002
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.571
Then Tails is running from USB drive "old" 0.684
And all tps features are active 1.935
When I write some files expected to persist 1.671
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.511
And all persistent directories from the old Tails version have safe access rights 2.785
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.270
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.215
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.006
Tags: @product
2:26.405
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.665
And I log in to a new session 21.866
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.506
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.143
Then the running Tails is installed on USB drive "to_upgrade" 17.434
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.094
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.764
Before features/support/hooks.rb:269 0.003
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.710
Then all tps features from the old Tails version are active 1.632
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.262
After features/support/hooks.rb:326 0.958
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:2.263
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.614
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.069
And Tor is ready 23.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.918
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.040
Given I shutdown Tails and wait for the computer to power off 8.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.063
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.463
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.462
When the network is plugged 0.069
And Tor is ready 19.418
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.736
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.476
Given I shutdown Tails and wait for the computer to power off 4.066
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.486
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.940
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.061
And Tor is ready 19.606
Then the Upgrader considers the system as up-to-date 0.288
# 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.386
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.719
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
36.971
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 10.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.959
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.242
After features/support/hooks.rb:326 0.597
After features/support/hooks.rb:100 0.000