Project Number Date
test_Tails_ISO_devel 3311 07 Mar 2024, 12:56

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 18:16.172 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:43.368
Before features/support/hooks.rb:245 0.007
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 21.769
When I start Tails from USB drive "old" with network unplugged 1:16.306
Then the boot device has safe access rights 2.981
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:291 3.696
After features/support/hooks.rb:75 0.014
Tags: @product
2:5.427
Before features/support/hooks.rb:245 0.009
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:12.307
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 41.893
And I take note of which tps features are available 1.855
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 8.033
After features/support/hooks.rb:291 0.181
After features/support/hooks.rb:75 0.012
Tags: @product
2:33.515
Before features/support/hooks.rb:245 0.008
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.636
Then Tails is running from USB drive "old" 0.365
And all tps features are active 1.723
When I write some files expected to persist 1.655
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.453
And I take note of which tps features are available 1.091
And I shutdown Tails and wait for the computer to power off 5.107
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.719
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.012
Tags: @product
2:30.952
Before features/support/hooks.rb:245 0.025
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.550
And I log in to a new session 16.088
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.420
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.093
Then the running Tails is installed on USB drive "to_upgrade" 13.005
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:291 20:0.707
After features/support/hooks.rb:75 0.000
Tags: @product
2:19.078
Before features/support/hooks.rb:245 0.007
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.958
Then all tps features from the old Tails version are active 1.423
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.049
And the expected persistent files created with the old Tails version are present in the filesystem 1.561
And all persistent directories from the old Tails version have safe access rights 2.537
After features/support/hooks.rb:291 0.842
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:32.369
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 11.893
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.028
And Tor is ready 19.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.172
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.503
Given I shutdown Tails and wait for the computer to power off 6.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.300
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.777
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.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.278
When the network is plugged 0.028
And Tor is ready 15.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.701
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.828
Given I shutdown Tails and wait for the computer to power off 5.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.774
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.908
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.029
And Tor is ready 15.356
Then the Upgrader considers the system as up-to-date 0.272
# 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.222
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.868
After features/support/hooks.rb:291 0.720
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
31.461
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 9.982
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.424
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 14.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.558
After features/support/hooks.rb:291 0.652
After features/support/hooks.rb:75 0.000