Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 40 12 Apr 2024, 21:02

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:2.760 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:33.837
Before features/support/hooks.rb:259 0.004
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 19.476
When I start Tails from USB drive "old" with network unplugged 1:9.435
Then the boot device has safe access rights 2.765
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:305 6.858
After features/support/hooks.rb:89 0.010
Tags: @product
2:8.010
Before features/support/hooks.rb:259 0.007
Given a computer 0.913
And I start Tails from USB drive "old" with network unplugged and I login 1:26.122
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.925
And I take note of which tps features are available 1.449
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 6.480
After features/support/hooks.rb:305 0.190
After features/support/hooks.rb:89 0.008
Tags: @product
2:28.432
Before features/support/hooks.rb:259 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.889
Then Tails is running from USB drive "old" 0.312
And all tps features are active 2.405
When I write some files expected to persist 1.940
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.343
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.977
After features/support/hooks.rb:305 0.149
After features/support/hooks.rb:89 0.010
Tags: @product
2:23.082
Before features/support/hooks.rb:259 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.016
And I log in to a new session 17.621
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.232
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.140
Then the running Tails is installed on USB drive "to_upgrade" 18.278
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:305 2.368
After features/support/hooks.rb:89 0.000
Tags: @product
2:1.798
Before features/support/hooks.rb:259 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.227
Then all tps features from the old Tails version are active 1.511
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 2.817
And the expected persistent files created with the old Tails version are present in the filesystem 1.305
And all persistent directories from the old Tails version have safe access rights 2.429
After features/support/hooks.rb:305 0.740
After features/support/hooks.rb:89 0.014
5:56.838
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.851
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.387
When the network is plugged 0.051
And Tor is ready 17.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.027
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.485
Given I shutdown Tails and wait for the computer to power off 6.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.503
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.980
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
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.267
# 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.235
When the network is plugged 0.046
And Tor is ready 17.710
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.142
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.736
Given I shutdown Tails and wait for the computer to power off 4.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.158
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
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.279
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.059
And Tor is ready 15.238
Then the Upgrader considers the system as up-to-date 10.628
# 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.125
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.865
After features/support/hooks.rb:305 0.675
After features/support/hooks.rb:89 0.019
30.760
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.650
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.509
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 13.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.221
After features/support/hooks.rb:305 1.647
After features/support/hooks.rb:89 0.000