Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 82 24 May 2024, 06:44

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 19:50.437 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:59.803
Before features/support/hooks.rb:259 0.006
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.606
When I start Tails from USB drive "old" with network unplugged 1:24.697
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:305 7.111
After features/support/hooks.rb:89 0.008
Tags: @product
2:18.801
Before features/support/hooks.rb:259 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:26.430
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 40.115
And I take note of which tps features are available 1.813
Then a Tails persistence partition exists on USB drive "old" 0.936
And I shutdown Tails and wait for the computer to power off 8.956
After features/support/hooks.rb:305 0.230
After features/support/hooks.rb:89 0.009
Tags: @product
2:56.880
Before features/support/hooks.rb:259 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.356
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.055
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.886
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.327
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.747
After features/support/hooks.rb:305 0.132
After features/support/hooks.rb:89 0.017
Tags: @product
2:26.908
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.007
And I log in to a new session 18.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.166
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.210
Then the running Tails is installed on USB drive "to_upgrade" 16.722
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.181
After features/support/hooks.rb:305 3.835
After features/support/hooks.rb:89 0.000
Tags: @product
2:21.077
Before features/support/hooks.rb:259 0.004
Given a computer 1.503
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.765
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.261
And the expected persistent files created with the old Tails version are present in the filesystem 1.709
And all persistent directories from the old Tails version have safe access rights 2.745
After features/support/hooks.rb:305 0.657
After features/support/hooks.rb:89 0.009
7:9.543
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.767
And no SquashFS delta is installed 0.265
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.045
And Tor is ready 20.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.904
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.309
Given I shutdown Tails and wait for the computer to power off 11.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.472
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.277
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
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.427
# 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.291
When the network is plugged 0.044
And Tor is ready 21.083
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.342
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.394
Given I shutdown Tails and wait for the computer to power off 6.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.270
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.414
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.376
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.051
And Tor is ready 17.196
Then the Upgrader considers the system as up-to-date 10.877
# 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.298
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.877
After features/support/hooks.rb:305 0.758
After features/support/hooks.rb:89 0.054
37.423
Before features/support/hooks.rb:259 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 1.078
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 19.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.711
After features/support/hooks.rb:305 0.758
After features/support/hooks.rb:89 0.000