Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 18 15 Oct 2024, 01:06

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:53.228 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:0.670
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.254
When I start Tails from USB drive "old" with network unplugged 1:26.956
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.715
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.756
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:30.899
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.766
And I take note of which tps features are available 1.483
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.260
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.012
Tags: @product
2:49.072
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.428
Then Tails is running from USB drive "old" 1.515
And all tps features are active 1.991
When I write some files expected to persist 1.664
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 3.608
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.529
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.875
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.305
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.810
And I log in to a new session 18.954
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.529
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.135
Then the running Tails is installed on USB drive "to_upgrade" 17.040
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 3.021
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.394
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.471
Then all tps features from the old Tails version are active 1.585
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 2.986
And the expected persistent files created with the old Tails version are present in the filesystem 1.509
And all persistent directories from the old Tails version have safe access rights 2.351
After features/support/hooks.rb:326 0.611
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:33.079
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.164
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.111
And Tor is ready 21.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.496
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.614
Given I shutdown Tails and wait for the computer to power off 10.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.063
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
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.302
# 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.253
When the network is plugged 0.080
And Tor is ready 19.480
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.957
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.425
Given I shutdown Tails and wait for the computer to power off 4.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.990
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.091
And Tor is ready 18.987
Then the Upgrader considers the system as up-to-date 0.318
# 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.419
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.916
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.948
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 9.682
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.787
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 19.237
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.814
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.000