Project Number Date
test_Tails_ISO_devel 3546 12 Oct 2024, 13:00

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:19.178 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:9.449
Before features/support/hooks.rb:269 0.005
Given a computer 0.420
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.541
When I start Tails from USB drive "old" with network unplugged 1:31.598
Then the boot device has safe access rights 3.653
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.398
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.563
After features/support/hooks.rb:100 0.030
Tags: @product
2:15.988
Before features/support/hooks.rb:269 0.006
Given a computer 0.329
And I start Tails from USB drive "old" with network unplugged and I login 1:31.760
Then Tails is running from USB drive "old" 0.406
And I create a persistent partition 32.576
And I take note of which tps features are available 1.496
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 8.493
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.756
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.620
Then Tails is running from USB drive "old" 1.671
And all tps features are active 2.120
When I write some files expected to persist 2.265
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.521
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 2.554
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 6.266
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.591
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.616
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 12.432
And I log in to a new session 20.847
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.151
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.549
Then the running Tails is installed on USB drive "to_upgrade" 24.734
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.912
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.327
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.263
Then all tps features from the old Tails version are active 3.165
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.273
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.553
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:57.699
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 13.517
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.071
And Tor is ready 22.430
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.037
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.779
Given I shutdown Tails and wait for the computer to power off 15.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.507
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.305
When the network is plugged 0.068
And Tor is ready 21.276
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.398
Given I shutdown Tails and wait for the computer to power off 4.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.079
Then Tails is running version 6.3~testoverlayfs 0.033
And all tps features are active 2.384
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.063
And Tor is ready 21.824
Then the Upgrader considers the system as up-to-date 0.347
# 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.218
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 1.012
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.339
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 11.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.840
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.000