Project Number Date
test_Tails_ISO_devel 3499 01 Sep 2024, 12:15

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:14.503 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
1:55.825
Before features/support/hooks.rb:269 0.008
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.763
When I start Tails from USB drive "old" with network unplugged 1:20.899
Then the boot device has safe access rights 2.889
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 0.921
After features/support/hooks.rb:100 0.044
Tags: @product
2:2.709
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:20.932
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 30.717
And I take note of which tps features are available 1.328
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.361
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.011
Tags: @product
2:43.469
Before features/support/hooks.rb:269 0.008
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.049
Then Tails is running from USB drive "old" 0.365
And all tps features are active 1.897
When I write some files expected to persist 1.652
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.607
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.286
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.382
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.211
Before features/support/hooks.rb:269 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 10.573
And I log in to a new session 18.652
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.045
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.503
Then the running Tails is installed on USB drive "to_upgrade" 18.598
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.827
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.084
Before features/support/hooks.rb:269 0.008
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.319
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 2.936
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.459
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:16.265
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.535
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.064
And Tor is ready 17.354
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.645
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.436
Given I shutdown Tails and wait for the computer to power off 10.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.946
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.301
When the network is plugged 0.063
And Tor is ready 19.528
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.850
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.334
Given I shutdown Tails and wait for the computer to power off 4.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.988
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.933
And the file system changes introduced in version 6.3~testoverlayfs are present 0.547
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.539
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.073
And Tor is ready 16.778
Then the Upgrader considers the system as up-to-date 0.344
# 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 13.591
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.905
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.936
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.707
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 17.127
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.462
After features/support/hooks.rb:326 1.342
After features/support/hooks.rb:100 0.000