Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 25 05 Apr 2025, 13:57

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:36.474 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:23.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 33.396
When I start Tails from USB drive "old" with network unplugged 1:44.734
Then the boot device has safe access rights 2.985
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:330 9.905
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:34.711
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 31.244
And I take note of which tps features are available 2.336
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.275
After features/support/hooks.rb:330 0.233
After features/support/hooks.rb:100 0.017
Tags: @product
3:10.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.310
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.540
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.087
When I write some files expected to persist 2.168
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 3.075
And I take note of which tps features are available 0.570
And I shutdown Tails and wait for the computer to power off 7.014
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.968
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.883
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.478
And I log in to a new session 19.597
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.981
And I plug USB drive "to_upgrade" 2.640
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.866
Then the running Tails is installed on USB drive "to_upgrade" 27.858
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 7.243
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.471
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.693
After features/support/hooks.rb:330 1.448
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:55.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.733
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.532
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.449
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.111
And Tor is ready 23.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.561
Given I shutdown Tails and wait for the computer to power off 9.066
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.181
Then Tails is running version 6.2~testoverlayfs 0.083
And all tps features are active 2.561
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.286
When the network is plugged 0.077
And Tor is ready 19.088
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.206
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.768
Given I shutdown Tails and wait for the computer to power off 4.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.582
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.422
And the file system changes introduced in version 6.3~testoverlayfs are present 0.641
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.464
When the network is plugged 0.074
And Tor is ready 21.438
Then the Upgrader considers the system as up-to-date 0.383
# 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 17.631
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.132
After features/support/hooks.rb:330 1.216
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
41.761
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 with a persistent partition enabled and logged in 10.823
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 21.158
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.159
After features/support/hooks.rb:330 1.600
After features/support/hooks.rb:100 0.000