Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 20 31 Mar 2025, 13:16

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:22.026 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:17.997
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 34.539
When I start Tails from USB drive "old" with network unplugged 1:37.171
Then the boot device has safe access rights 3.668
And Tails is running from USB drive "old" 0.490
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.284
After features/support/hooks.rb:330 3.730
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:27.920
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 36.000
And I take note of which tps features are available 1.480
Then a Tails persistence partition exists on USB drive "old" 0.932
And I shutdown Tails and wait for the computer to power off 7.662
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.011
Tags: @product
3:1.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.182
Then Tails is running from USB drive "old" 1.396
And all tps features are active 2.496
When I write some files expected to persist 2.043
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.293
And all persistence configuration files have safe access rights 0.655
And all persistent directories from the old Tails version have safe access rights 2.666
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 6.555
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.026
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.548
And I log in to a new session 20.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.317
And I plug USB drive "to_upgrade" 2.510
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.948
Then the running Tails is installed on USB drive "to_upgrade" 23.135
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 1.202
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.098
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.054
Then all tps features from the old Tails version are active 1.944
And Tails is running from USB drive "to_upgrade" 0.455
And the boot device has safe access rights 4.274
And the expected persistent files created with the old Tails version are present in the filesystem 2.677
And all persistent directories from the old Tails version have safe access rights 3.422
After features/support/hooks.rb:330 1.135
After features/support/hooks.rb:100 0.021
8:45.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.720
And no SquashFS delta is installed 0.756
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
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.581
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.638
When the network is plugged 0.135
And Tor is ready 25.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.302
Given I shutdown Tails and wait for the computer to power off 1:31.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.957
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.703
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
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.296
# 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.348
When the network is plugged 0.126
And Tor is ready 22.514
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.372
Given I shutdown Tails and wait for the computer to power off 6.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.588
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.123
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.073
And Tor is ready 20.694
Then the Upgrader considers the system as up-to-date 0.342
# 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.405
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.082
After features/support/hooks.rb:330 1.231
After features/support/hooks.rb:100 0.044
44.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.651
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.103
But a current signing key is available on our website 0.000
When the network is plugged 0.220
And Tor is ready 21.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.883
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.000