Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 116 24 Jun 2024, 06:42

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:49.384 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.117
Before features/support/hooks.rb:269 0.006
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.660
When I start Tails from USB drive "old" with network unplugged 2:1.185
Then the boot device has safe access rights 2.916
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.530
After features/support/hooks.rb:100 0.069
Tags: @product
2:9.558
Before features/support/hooks.rb:269 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:23.981
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 34.266
And I take note of which tps features are available 1.553
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.388
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.115
Before features/support/hooks.rb:269 0.005
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.896
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.605
When I write some files expected to persist 2.159
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.575
And all persistent directories from the old Tails version have safe access rights 3.006
And I take note of which tps features are available 0.705
And I shutdown Tails and wait for the computer to power off 4.451
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.759
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.013
Tags: @product
2:38.851
Before features/support/hooks.rb:269 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 13.242
And I log in to a new session 22.713
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.802
And I plug USB drive "to_upgrade" 2.581
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.839
Then the running Tails is installed on USB drive "to_upgrade" 22.239
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.686
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.874
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.891
Then all tps features from the old Tails version are active 1.820
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.307
And the expected persistent files created with the old Tails version are present in the filesystem 1.790
And all persistent directories from the old Tails version have safe access rights 2.481
After features/support/hooks.rb:326 0.976
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:36.274
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.783
And no SquashFS delta is installed 0.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.593
When the network is plugged 0.049
And Tor is ready 20.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.209
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.008
Given I shutdown Tails and wait for the computer to power off 13.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.453
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.184
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.329
When the network is plugged 0.040
And Tor is ready 21.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.896
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.879
Given I shutdown Tails and wait for the computer to power off 4.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.943
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.138
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.133
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.051
And Tor is ready 19.453
Then the Upgrader considers the system as up-to-date 0.328
# 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.476
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.593
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.919
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.967
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 18.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.249
After features/support/hooks.rb:326 0.976
After features/support/hooks.rb:100 0.000