Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 18 23 Mar 2024, 06:27

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 17:25.321 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
1:38.277
Before features/support/hooks.rb:245 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 24.585
When I start Tails from USB drive "old" with network unplugged 1:8.250
Then the boot device has safe access rights 3.180
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:291 6.758
After features/support/hooks.rb:75 0.009
Tags: @product
2:2.164
Before features/support/hooks.rb:245 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:14.471
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 35.967
And I take note of which tps features are available 1.472
Then a Tails persistence partition exists on USB drive "old" 0.740
And I shutdown Tails and wait for the computer to power off 9.024
After features/support/hooks.rb:291 0.138
After features/support/hooks.rb:75 0.008
Tags: @product
2:32.432
Before features/support/hooks.rb:245 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.624
Then Tails is running from USB drive "old" 0.348
And all tps features are active 1.787
When I write some files expected to persist 1.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.747
And I take note of which tps features are available 0.425
And I shutdown Tails and wait for the computer to power off 4.020
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.921
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.009
Tags: @product
2:20.459
Before features/support/hooks.rb:245 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 10.918
And I log in to a new session 16.100
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.265
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.185
Then the running Tails is installed on USB drive "to_upgrade" 13.238
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 6.578
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.109
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.989
Then all tps features from the old Tails version are active 1.480
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.934
And the expected persistent files created with the old Tails version are present in the filesystem 1.784
And all persistent directories from the old Tails version have safe access rights 2.418
After features/support/hooks.rb:291 0.787
After features/support/hooks.rb:75 0.010
5:50.896
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.804
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.036
And Tor is ready 18.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.056
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.518
Given I shutdown Tails and wait for the computer to power off 6.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.799
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.961
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.280
# 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.246
When the network is plugged 0.032
And Tor is ready 18.250
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.608
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.057
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.242
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.041
And Tor is ready 19.446
Then the Upgrader considers the system as up-to-date 0.225
# 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.500
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.876
After features/support/hooks.rb:291 0.828
After features/support/hooks.rb:75 0.017
57.982
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.501
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.500
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 41.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.612
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.000