Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 73 15 May 2024, 06:43

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:34.503 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.097
Before features/support/hooks.rb:259 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.451
When I start Tails from USB drive "old" with network unplugged 1:38.952
Then the boot device has safe access rights 3.230
And Tails is running from USB drive "old" 0.413
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.139
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:305 7.027
After features/support/hooks.rb:89 0.010
Tags: @product
2:8.916
Before features/support/hooks.rb:259 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:21.120
Then Tails is running from USB drive "old" 1.080
And I create a persistent partition 35.274
And I take note of which tps features are available 1.908
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 8.416
After features/support/hooks.rb:305 0.265
After features/support/hooks.rb:89 0.011
Tags: @product
2:55.766
Before features/support/hooks.rb:259 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.142
Then Tails is running from USB drive "old" 0.440
And all tps features are active 2.288
When I write some files expected to persist 1.861
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.617
And all persistent directories from the old Tails version have safe access rights 2.618
And I take note of which tps features are available 0.530
And I shutdown Tails and wait for the computer to power off 4.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.698
After features/support/hooks.rb:305 0.105
After features/support/hooks.rb:89 0.010
Tags: @product
2:33.391
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.344
And I log in to a new session 22.472
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.900
And I plug USB drive "to_upgrade" 2.534
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.202
Then the running Tails is installed on USB drive "to_upgrade" 18.520
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:305 3.930
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.791
Before features/support/hooks.rb:259 0.007
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.595
Then all tps features from the old Tails version are active 1.892
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.190
And the expected persistent files created with the old Tails version are present in the filesystem 1.704
And all persistent directories from the old Tails version have safe access rights 2.848
After features/support/hooks.rb:305 0.843
After features/support/hooks.rb:89 0.012
6:44.439
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.676
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.037
And Tor is ready 25.129
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.011
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.760
Given I shutdown Tails and wait for the computer to power off 9.148
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.009
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 6.146
And the file system changes introduced in version 6.2~testoverlayfs are present 0.420
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.410
# 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.351
When the network is plugged 0.041
And Tor is ready 20.196
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.779
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.271
Given I shutdown Tails and wait for the computer to power off 6.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.148
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.669
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.056
And Tor is ready 20.571
Then the Upgrader considers the system as up-to-date 0.292
# 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 15.075
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.906
After features/support/hooks.rb:305 0.735
After features/support/hooks.rb:89 0.020
38.100
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 13.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.761
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 17.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.758
After features/support/hooks.rb:305 0.671
After features/support/hooks.rb:89 0.000