Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 70 10 May 2024, 06:51

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:39.988 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:18.926
Before features/support/hooks.rb:259 0.006
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 32.152
When I start Tails from USB drive "old" with network unplugged 1:41.066
Then the boot device has safe access rights 3.266
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:305 3.658
After features/support/hooks.rb:89 0.012
Tags: @product
2:16.829
Before features/support/hooks.rb:259 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:25.241
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 37.431
And I take note of which tps features are available 1.865
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 10.900
After features/support/hooks.rb:305 0.168
After features/support/hooks.rb:89 0.009
Tags: @product
2:53.801
Before features/support/hooks.rb:259 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.859
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.335
When I write some files expected to persist 1.997
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.515
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.543
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.851
After features/support/hooks.rb:305 0.131
After features/support/hooks.rb:89 0.009
Tags: @product
2:25.527
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.026
And I log in to a new session 17.018
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.367
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.319
Then the running Tails is installed on USB drive "to_upgrade" 18.965
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 0.891
After features/support/hooks.rb:89 0.000
Tags: @product
2:20.208
Before features/support/hooks.rb:259 0.008
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.559
Then all tps features from the old Tails version are active 1.986
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.762
And the expected persistent files created with the old Tails version are present in the filesystem 1.660
And all persistent directories from the old Tails version have safe access rights 2.670
After features/support/hooks.rb:305 0.714
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
7:44.226
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 11.733
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
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.523
When the network is plugged 0.368
And Tor is ready 23.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.937
Given I shutdown Tails and wait for the computer to power off 1:20.869
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.003
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.495
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
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.409
# 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.282
When the network is plugged 0.040
And Tor is ready 20.859
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.232
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.060
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.571
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 4.380
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.037
And Tor is ready 17.691
Then the Upgrader considers the system as up-to-date 0.312
# 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.795
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:305 1.030
After features/support/hooks.rb:89 0.021
Tags: @product @automatic_upgrade
40.468
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.804
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.951
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 21.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.650
After features/support/hooks.rb:305 0.655
After features/support/hooks.rb:89 0.000