Project Number Date
test_Tails_ISO_stable 5269 15 Nov 2024, 20:33

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 18:59.923 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:5.607
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 31.054
When I start Tails from USB drive "old" with network unplugged 1:29.046
Then the boot device has safe access rights 3.125
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 7.263
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.127
Before features/support/hooks.rb:269 0.007
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:25.154
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 37.344
And I take note of which tps features are available 1.736
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 10.400
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.011
Tags: @product
2:54.113
Before features/support/hooks.rb:269 0.005
Given a computer 0.891
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.929
Then Tails is running from USB drive "old" 1.612
And all tps features are active 2.001
When I write some files expected to persist 2.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 0.405
And I shutdown Tails and wait for the computer to power off 4.239
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.977
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.256
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 10.849
And I log in to a new session 18.727
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.715
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.521
Then the running Tails is installed on USB drive "to_upgrade" 19.544
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.280
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.252
Before features/support/hooks.rb:269 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.548
Then all tps features from the old Tails version are active 1.811
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.350
And the expected persistent files created with the old Tails version are present in the filesystem 1.627
And all persistent directories from the old Tails version have safe access rights 2.367
After features/support/hooks.rb:326 0.880
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:31.395
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 12.805
And no SquashFS delta is installed 0.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.069
And Tor is ready 23.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.183
Given I shutdown Tails and wait for the computer to power off 8.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.336
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.350
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.378
When the network is plugged 0.066
And Tor is ready 19.046
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.541
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.951
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.665
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.235
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.373
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.422
And Tor is ready 16.429
Then the Upgrader considers the system as up-to-date 10.822
# 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.029
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.762
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.169
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 10.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.837
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 15.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.432
After features/support/hooks.rb:326 0.948
After features/support/hooks.rb:100 0.000