Project Number Date
test_Tails_ISO_devel 3413 03 Jun 2024, 22:42

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:24.047 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:16.604
Before features/support/hooks.rb:265 0.007
Given a computer 0.291
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.083
When I start Tails from USB drive "old" with network unplugged 1:40.945
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:311 3.586
After features/support/hooks.rb:100 0.069
Tags: @product
2:18.396
Before features/support/hooks.rb:265 0.008
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:29.308
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 37.029
And I take note of which tps features are available 1.927
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 8.671
After features/support/hooks.rb:311 0.145
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.707
Before features/support/hooks.rb:265 0.007
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.547
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.898
When I write some files expected to persist 2.162
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.360
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.397
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.555
After features/support/hooks.rb:311 0.175
After features/support/hooks.rb:100 0.012
Tags: @product
2:33.891
Before features/support/hooks.rb:265 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.952
And I log in to a new session 22.090
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.718
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.235
Then the running Tails is installed on USB drive "to_upgrade" 19.993
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:311 3.655
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.910
Before features/support/hooks.rb:265 0.009
Given a computer 0.473
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.484
Then all tps features from the old Tails version are active 1.780
And Tails is running from USB drive "to_upgrade" 0.432
And the boot device has safe access rights 3.485
And the expected persistent files created with the old Tails version are present in the filesystem 1.646
And all persistent directories from the old Tails version have safe access rights 2.606
After features/support/hooks.rb:311 0.812
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:11.581
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.923
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.042
And Tor is ready 19.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.545
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.784
Given I shutdown Tails and wait for the computer to power off 9.554
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.873
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.162
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
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.427
# 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.289
When the network is plugged 0.037
And Tor is ready 18.806
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.260
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.551
Given I shutdown Tails and wait for the computer to power off 4.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.356
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.383
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.047
And Tor is ready 45.816
Then the Upgrader considers the system as up-to-date 0.318
# 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 15.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.968
After features/support/hooks.rb:311 0.694
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.956
Before features/support/hooks.rb:265 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.427
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.975
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 17.256
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.858
After features/support/hooks.rb:311 1.105
After features/support/hooks.rb:100 0.000