Project Number Date
test_Tails_ISO_devel 3574 02 Nov 2024, 12:56

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:48.627 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:24.099
Before features/support/hooks.rb:269 0.007
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 38.362
When I start Tails from USB drive "old" with network unplugged 1:39.913
Then the boot device has safe access rights 3.390
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:326 3.518
After features/support/hooks.rb:100 0.014
Tags: @product
2:19.691
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:34.157
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 33.902
And I take note of which tps features are available 1.635
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 8.474
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.060
Before features/support/hooks.rb:269 0.008
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.835
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.572
When I write some files expected to persist 2.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 3.011
And I take note of which tps features are available 0.595
And I shutdown Tails and wait for the computer to power off 4.735
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.837
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.787
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 12.490
And I log in to a new session 20.220
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.053
And I plug USB drive "to_upgrade" 2.501
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.754
Then the running Tails is installed on USB drive "to_upgrade" 26.295
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 1.062
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.511
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.956
Then all tps features from the old Tails version are active 1.912
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.822
And the expected persistent files created with the old Tails version are present in the filesystem 1.648
And all persistent directories from the old Tails version have safe access rights 2.594
After features/support/hooks.rb:326 0.863
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:49.841
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.987
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.074
And Tor is ready 22.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.890
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.200
Given I shutdown Tails and wait for the computer to power off 8.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.999
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.494
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
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.385
# 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.295
When the network is plugged 0.075
And Tor is ready 21.655
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.266
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.125
Given I shutdown Tails and wait for the computer to power off 4.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.179
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.585
And the file system changes introduced in version 6.3~testoverlayfs are present 0.603
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.104
And Tor is ready 19.146
Then the Upgrader considers the system as up-to-date 0.322
# 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 14.478
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.186
After features/support/hooks.rb:326 0.909
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
1:1.634
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.826
But a current signing key is available on our website 0.000
When the network is plugged 0.153
And Tor is ready 48.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.000