Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 17 22 Mar 2024, 06:15

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:30.604 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
1:42.980
Before features/support/hooks.rb:245 0.007
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 25.532
When I start Tails from USB drive "old" with network unplugged 1:12.368
Then the boot device has safe access rights 2.821
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 6.847
After features/support/hooks.rb:75 0.010
Tags: @product
2:5.640
Before features/support/hooks.rb:245 0.007
Given a computer 0.379
And I start Tails from USB drive "old" with network unplugged and I login 1:23.343
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.403
And I take note of which tps features are available 1.293
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 7.105
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.586
Before features/support/hooks.rb:245 0.008
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.959
Then Tails is running from USB drive "old" 0.372
And all tps features are active 1.683
When I write some files expected to persist 1.619
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.495
And I take note of which tps features are available 0.377
And I shutdown Tails and wait for the computer to power off 4.221
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.122
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.236
Before features/support/hooks.rb:245 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 10.873
And I log in to a new session 16.185
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.710
Then the running Tails is installed on USB drive "to_upgrade" 14.940
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:291 1.675
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.526
Before features/support/hooks.rb:245 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.774
Then all tps features from the old Tails version are active 1.419
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 2.956
And the expected persistent files created with the old Tails version are present in the filesystem 1.255
And all persistent directories from the old Tails version have safe access rights 2.547
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:1.510
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.572
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
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.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.045
And Tor is ready 19.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.757
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.093
Given I shutdown Tails and wait for the computer to power off 11.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.707
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.890
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
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.318
# 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.309
When the network is plugged 0.031
And Tor is ready 17.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.483
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.154
Given I shutdown Tails and wait for the computer to power off 5.055
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.922
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.702
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.034
And Tor is ready 17.927
Then the Upgrader considers the system as up-to-date 0.246
# 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.364
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
36.124
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.244
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
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.769
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 16.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.794
After features/support/hooks.rb:291 0.654
After features/support/hooks.rb:75 0.000