Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 44 16 Apr 2024, 06:24

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:3.808 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:38.112
Before features/support/hooks.rb:259 0.005
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 20.024
When I start Tails from USB drive "old" with network unplugged 1:12.748
Then the boot device has safe access rights 2.995
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:305 0.904
After features/support/hooks.rb:89 0.009
Tags: @product
1:59.328
Before features/support/hooks.rb:259 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:15.956
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 32.423
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.284
After features/support/hooks.rb:305 0.169
After features/support/hooks.rb:89 0.009
Tags: @product
2:27.385
Before features/support/hooks.rb:259 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.966
Then Tails is running from USB drive "old" 0.365
And all tps features are active 2.006
When I write some files expected to persist 1.580
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.564
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.730
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.858
After features/support/hooks.rb:305 0.136
After features/support/hooks.rb:89 0.010
Tags: @product
2:28.491
Before features/support/hooks.rb:259 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 19.436
And I log in to a new session 15.173
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.407
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.702
Then the running Tails is installed on USB drive "to_upgrade" 13.969
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:305 6.805
After features/support/hooks.rb:89 0.000
Tags: @product
1:59.004
Before features/support/hooks.rb:259 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.979
Then all tps features from the old Tails version are active 1.551
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.283
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.351
After features/support/hooks.rb:305 0.714
After features/support/hooks.rb:89 0.012
5:59.264
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.150
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.049
And Tor is ready 16.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.191
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.756
Given I shutdown Tails and wait for the computer to power off 6.905
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.902
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.481
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.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.267
# 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.321
When the network is plugged 0.043
And Tor is ready 16.131
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.166
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.110
Given I shutdown Tails and wait for the computer to power off 4.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.399
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.843
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.060
And Tor is ready 17.634
Then the Upgrader considers the system as up-to-date 0.225
# 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.502
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.991
After features/support/hooks.rb:305 0.710
After features/support/hooks.rb:89 0.022
32.221
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 9.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.549
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 15.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.372
After features/support/hooks.rb:305 1.681
After features/support/hooks.rb:89 0.000