Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 113 21 Jun 2024, 06:49

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 20:0.655 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:37.889
Before features/support/hooks.rb:269 0.007
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 33.445
When I start Tails from USB drive "old" with network unplugged 1:58.700
Then the boot device has safe access rights 3.331
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:326 3.896
After features/support/hooks.rb:100 0.015
Tags: @product
2:7.709
Before features/support/hooks.rb:269 0.009
Given a computer 0.339
And I start Tails from USB drive "old" with network unplugged and I login 1:24.195
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 31.407
And I take note of which tps features are available 1.676
Then a Tails persistence partition exists on USB drive "old" 0.941
And I shutdown Tails and wait for the computer to power off 8.777
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.430
Before features/support/hooks.rb:269 0.007
Given a computer 0.350
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.851
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.297
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 3.166
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.306
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.006
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.553
Before features/support/hooks.rb:269 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 11.524
And I log in to a new session 19.523
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.718
And I plug USB drive "to_upgrade" 2.610
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.304
Then the running Tails is installed on USB drive "to_upgrade" 18.412
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 3.583
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.140
Before features/support/hooks.rb:269 0.009
Given a computer 0.288
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.372
Then all tps features from the old Tails version are active 1.643
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.590
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.512
After features/support/hooks.rb:326 0.685
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
6:41.704
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.244
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.047
And Tor is ready 19.772
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.620
Given I shutdown Tails and wait for the computer to power off 8.674
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.994
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.146
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.423
# 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.290
When the network is plugged 0.114
And Tor is ready 19.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.549
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.992
Given I shutdown Tails and wait for the computer to power off 4.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.351
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.599
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.044
And Tor is ready 21.482
Then the Upgrader considers the system as up-to-date 0.338
# 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.813
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
51.227
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 1.744
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 18.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.390
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.000