Project Number Date
test_Tails_ISO_stable 4862 30 May 2024, 20:07

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 22:31.217 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:21.375
Before features/support/hooks.rb:265 0.009
Given a computer 0.320
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 39.769
When I start Tails from USB drive "old" with network unplugged 1:35.764
Then the boot device has safe access rights 3.316
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:311 3.781
After features/support/hooks.rb:100 0.013
Tags: @product
2:17.856
Before features/support/hooks.rb:265 0.006
Given a computer 0.389
And I start Tails from USB drive "old" with network unplugged and I login 1:26.551
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 39.481
And I take note of which tps features are available 2.679
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 7.506
After features/support/hooks.rb:311 0.228
After features/support/hooks.rb:100 0.012
Tags: @product
3:16.011
Before features/support/hooks.rb:265 0.024
Given a computer 0.720
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.140
Then Tails is running from USB drive "old" 0.374
And all tps features are active 2.363
When I write some files expected to persist 1.800
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.585
And all persistent directories from the old Tails version have safe access rights 2.833
And I take note of which tps features are available 0.620
And I shutdown Tails and wait for the computer to power off 4.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.248
After features/support/hooks.rb:311 0.174
After features/support/hooks.rb:100 0.011
Tags: @product
2:44.971
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 23.190
And I log in to a new session 19.088
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.852
And I plug USB drive "to_upgrade" 2.721
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.097
Then the running Tails is installed on USB drive "to_upgrade" 19.431
And I unplug USB drive "to_upgrade" 0.377
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:311 3.654
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.685
Before features/support/hooks.rb:265 0.006
Given a computer 2.151
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.061
Then all tps features from the old Tails version are active 2.044
And Tails is running from USB drive "to_upgrade" 0.440
And the boot device has safe access rights 4.053
And the expected persistent files created with the old Tails version are present in the filesystem 1.821
And all persistent directories from the old Tails version have safe access rights 3.111
After features/support/hooks.rb:311 0.836
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
8:17.247
Before features/support/hooks.rb:265 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 43.100
And no SquashFS delta is installed 0.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.417
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.709
When the network is plugged 0.460
And Tor is ready 23.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.487
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.976
Given I shutdown Tails and wait for the computer to power off 11.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.403
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.922
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.371
# 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.352
When the network is plugged 0.043
And Tor is ready 19.671
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.158
Given I shutdown Tails and wait for the computer to power off 4.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.474
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.422
And the file system changes introduced in version 6.3~testoverlayfs are present 0.640
And only the 6.3~testoverlayfs SquashFS delta is installed 0.115
# 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.501
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.378
When the network is plugged 0.103
And Tor is ready 17.814
Then the Upgrader considers the system as up-to-date 0.326
# 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.033
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.061
After features/support/hooks.rb:311 0.803
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
58.068
Before features/support/hooks.rb:265 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.912
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.123
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 45.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.614
After features/support/hooks.rb:311 0.753
After features/support/hooks.rb:100 0.000