Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 68 08 May 2024, 07:11

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:13.674 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:17.147
Before features/support/hooks.rb:259 0.006
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 33.577
When I start Tails from USB drive "old" with network unplugged 1:36.806
Then the boot device has safe access rights 4.268
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.376
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:305 3.755
After features/support/hooks.rb:89 0.009
Tags: @product
2:20.093
Before features/support/hooks.rb:259 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:30.929
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 37.681
And I take note of which tps features are available 1.487
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.564
After features/support/hooks.rb:305 0.165
After features/support/hooks.rb:89 0.011
Tags: @product
2:51.537
Before features/support/hooks.rb:259 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.065
Then Tails is running from USB drive "old" 0.393
And all tps features are active 2.891
When I write some files expected to persist 1.849
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.990
And I take note of which tps features are available 1.124
And I shutdown Tails and wait for the computer to power off 4.650
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.699
After features/support/hooks.rb:305 0.137
After features/support/hooks.rb:89 0.010
Tags: @product
2:30.907
Before features/support/hooks.rb:259 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.619
And I log in to a new session 19.084
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.572
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.423
Then the running Tails is installed on USB drive "to_upgrade" 19.403
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:305 6.720
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.734
Before features/support/hooks.rb:259 0.006
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.944
Then all tps features from the old Tails version are active 1.853
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.186
And the expected persistent files created with the old Tails version are present in the filesystem 1.745
And all persistent directories from the old Tails version have safe access rights 2.440
After features/support/hooks.rb:305 0.961
After features/support/hooks.rb:89 0.037
Tags: @product @automatic_upgrade
6:24.059
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.583
And no SquashFS delta is installed 0.083
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.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.034
And Tor is ready 22.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.058
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.471
Given I shutdown Tails and wait for the computer to power off 9.126
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.605
Then Tails is running version 6.2~testoverlayfs 0.032
And all tps features are active 2.582
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.393
# 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.310
When the network is plugged 0.058
And Tor is ready 16.327
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.819
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.700
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.186
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.225
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.062
# 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.395
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.037
And Tor is ready 20.194
Then the Upgrader considers the system as up-to-date 0.295
# 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.914
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.065
After features/support/hooks.rb:305 0.864
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
33.193
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.577
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.570
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 17.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.135
After features/support/hooks.rb:305 0.787
After features/support/hooks.rb:89 0.000