Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 53 24 Apr 2024, 19:02

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:47.626 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:15.488
Before features/support/hooks.rb:259 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.780
When I start Tails from USB drive "old" with network unplugged 1:36.997
Then the boot device has safe access rights 3.242
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:305 3.531
After features/support/hooks.rb:89 0.012
Tags: @product
2:16.775
Before features/support/hooks.rb:259 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:24.978
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 38.182
And I take note of which tps features are available 2.078
Then a Tails persistence partition exists on USB drive "old" 0.994
And I shutdown Tails and wait for the computer to power off 10.039
After features/support/hooks.rb:305 0.143
After features/support/hooks.rb:89 0.009
Tags: @product
2:56.142
Before features/support/hooks.rb:259 0.005
Given a computer 1.292
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.783
Then Tails is running from USB drive "old" 0.441
And all tps features are active 2.262
When I write some files expected to persist 1.994
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.499
And all persistent directories from the old Tails version have safe access rights 2.853
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.407
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.782
After features/support/hooks.rb:305 0.116
After features/support/hooks.rb:89 0.010
Tags: @product
2:30.432
Before features/support/hooks.rb:259 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 12.542
And I log in to a new session 22.769
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.988
And I plug USB drive "to_upgrade" 2.584
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.767
Then the running Tails is installed on USB drive "to_upgrade" 16.359
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:305 2.314
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.978
Before features/support/hooks.rb:259 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.893
Then all tps features from the old Tails version are active 1.727
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.047
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 3.155
After features/support/hooks.rb:305 0.671
After features/support/hooks.rb:89 0.014
6:49.566
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 14.975
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.420
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.048
And Tor is ready 24.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.091
Given I shutdown Tails and wait for the computer to power off 8.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.913
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.312
When the network is plugged 0.033
And Tor is ready 20.133
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.112
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.300
Given I shutdown Tails and wait for the computer to power off 6.751
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.283
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.123
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.056
And Tor is ready 18.555
Then the Upgrader considers the system as up-to-date 0.358
# 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 16.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.947
After features/support/hooks.rb:305 0.817
After features/support/hooks.rb:89 0.019
40.242
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 11.235
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.057
And the signing key used by the Upgrader is outdated 0.544
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 22.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.774
After features/support/hooks.rb:305 0.679
After features/support/hooks.rb:89 0.000