Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 31 05 Apr 2024, 06:12

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:11.045 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:11.717
Before features/support/hooks.rb:259 0.005
Given a computer 0.154
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 51.860
When I start Tails from USB drive "old" with network unplugged 1:14.843
Then the boot device has safe access rights 2.851
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:305 6.794
After features/support/hooks.rb:89 0.009
Tags: @product
2:12.015
Before features/support/hooks.rb:259 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:27.403
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 33.823
And I take note of which tps features are available 1.263
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.200
After features/support/hooks.rb:305 0.196
After features/support/hooks.rb:89 0.007
Tags: @product
2:25.369
Before features/support/hooks.rb:259 0.006
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.672
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.753
When I write some files expected to persist 1.450
# 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.348
And all persistent directories from the old Tails version have safe access rights 2.167
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.250
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.607
After features/support/hooks.rb:305 0.090
After features/support/hooks.rb:89 0.008
Tags: @product
2:15.858
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.303
And I log in to a new session 15.241
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.439
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.003
Then the running Tails is installed on USB drive "to_upgrade" 12.037
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:305 6.654
After features/support/hooks.rb:89 0.000
Tags: @product
1:55.337
Before features/support/hooks.rb:259 0.006
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.845
Then all tps features from the old Tails version are active 1.510
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.803
And the expected persistent files created with the old Tails version are present in the filesystem 1.290
And all persistent directories from the old Tails version have safe access rights 2.449
After features/support/hooks.rb:305 0.660
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
5:40.724
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.159
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.042
And Tor is ready 18.672
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.329
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.551
Given I shutdown Tails and wait for the computer to power off 6.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.496
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.944
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.247
When the network is plugged 0.032
And Tor is ready 19.199
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.945
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.423
Given I shutdown Tails and wait for the computer to power off 4.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.875
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 1.796
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
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.268
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.049
And Tor is ready 17.675
Then the Upgrader considers the system as up-to-date 0.216
# 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.735
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.796
After features/support/hooks.rb:305 0.666
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
30.022
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.506
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.428
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 14.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.856
After features/support/hooks.rb:305 0.626
After features/support/hooks.rb:89 0.000