Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 10 27 Mar 2025, 13:37

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:56.884 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:31.654
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.909
When I start Tails from USB drive "old" with network unplugged 1:53.353
Then the boot device has safe access rights 3.695
And Tails is running from USB drive "old" 0.513
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.438
And I unplug USB drive "old" 0.245
After features/support/hooks.rb:330 4.107
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.410
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:35.248
Then Tails is running from USB drive "old" 0.461
And I create a persistent partition 32.544
And I take note of which tps features are available 2.622
Then a Tails persistence partition exists on USB drive "old" 1.025
And I shutdown Tails and wait for the computer to power off 7.314
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.492
Then Tails is running from USB drive "old" 0.362
And all tps features are active 3.315
When I write some files expected to persist 2.749
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.531
And all persistent directories from the old Tails version have safe access rights 3.056
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 6.589
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.119
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.091
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 12.692
And I log in to a new session 21.879
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.774
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.514
Then the running Tails is installed on USB drive "to_upgrade" 26.188
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.361
After features/support/hooks.rb:330 2.528
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.422
Then all tps features from the old Tails version are active 1.975
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.469
And the expected persistent files created with the old Tails version are present in the filesystem 1.522
And all persistent directories from the old Tails version have safe access rights 2.849
After features/support/hooks.rb:330 1.663
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:1.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.249
And no SquashFS delta is installed 0.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.386
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.575
When the network is plugged 0.072
And Tor is ready 24.030
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.905
Given I shutdown Tails and wait for the computer to power off 14.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.997
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.343
And the file system changes introduced in version 6.2~testoverlayfs are present 0.416
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.302
When the network is plugged 0.082
And Tor is ready 21.378
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.015
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.016
Given I shutdown Tails and wait for the computer to power off 4.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.492
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.928
And the file system changes introduced in version 6.3~testoverlayfs are present 0.747
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.071
And Tor is ready 15.164
Then the Upgrader considers the system as up-to-date 0.385
# 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.787
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.871
After features/support/hooks.rb:330 0.880
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.880
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.912
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.823
After features/support/hooks.rb:330 1.089
After features/support/hooks.rb:100 0.000