Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 20 25 Mar 2024, 06:14

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:0.205 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:36.495
Before features/support/hooks.rb:245 0.004
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 19.140
When I start Tails from USB drive "old" with network unplugged 1:11.683
Then the boot device has safe access rights 3.259
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:291 3.506
After features/support/hooks.rb:75 0.011
Tags: @product
1:58.695
Before features/support/hooks.rb:245 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:15.782
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 32.637
And I take note of which tps features are available 1.773
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 7.154
After features/support/hooks.rb:291 0.190
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.997
Before features/support/hooks.rb:245 0.007
Given a computer 0.513
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.232
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.024
When I write some files expected to persist 1.759
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.632
And all persistent directories from the old Tails version have safe access rights 2.713
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.148
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.926
After features/support/hooks.rb:291 0.222
After features/support/hooks.rb:75 0.009
Tags: @product
2:20.598
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.748
And I log in to a new session 16.298
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.365
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.600
Then the running Tails is installed on USB drive "to_upgrade" 12.835
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 3.544
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.631
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.546
Then all tps features from the old Tails version are active 1.541
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.877
And the expected persistent files created with the old Tails version are present in the filesystem 1.683
And all persistent directories from the old Tails version have safe access rights 2.490
After features/support/hooks.rb:291 0.991
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:0.159
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.776
And no SquashFS delta is installed 0.173
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.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.039
And Tor is ready 21.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.930
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.964
Given I shutdown Tails and wait for the computer to power off 6.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.449
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.264
When the network is plugged 0.047
And Tor is ready 17.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.482
Given I shutdown Tails and wait for the computer to power off 4.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.241
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.800
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.351
When the network is plugged 0.036
And Tor is ready 18.224
Then the Upgrader considers the system as up-to-date 0.248
# 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.308
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.822
After features/support/hooks.rb:291 0.968
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
33.627
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.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
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.674
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 17.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.190
After features/support/hooks.rb:291 0.609
After features/support/hooks.rb:75 0.000