Project Number Date
test_Tails_ISO_stable 4767 04 Apr 2024, 12:27

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:19.646 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:58.290
Before features/support/hooks.rb:245 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 43.697
When I start Tails from USB drive "old" with network unplugged 1:9.367
Then the boot device has safe access rights 2.922
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 6.745
After features/support/hooks.rb:75 0.011
Tags: @product
2:1.614
Before features/support/hooks.rb:245 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:19.144
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 31.455
And I take note of which tps features are available 1.343
Then a Tails persistence partition exists on USB drive "old" 0.802
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:291 0.210
After features/support/hooks.rb:75 0.014
Tags: @product
2:27.355
Before features/support/hooks.rb:245 0.010
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.011
Then Tails is running from USB drive "old" 0.385
And all tps features are active 1.967
When I write some files expected to persist 1.826
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.323
And I take note of which tps features are available 0.555
And I shutdown Tails and wait for the computer to power off 4.454
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.912
After features/support/hooks.rb:291 0.124
After features/support/hooks.rb:75 0.010
Tags: @product
2:18.939
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 9.832
And I log in to a new session 15.570
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.283
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.253
Then the running Tails is installed on USB drive "to_upgrade" 12.234
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:291 3.594
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.236
Before features/support/hooks.rb:245 0.005
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.402
Then all tps features from the old Tails version are active 1.518
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.902
And the expected persistent files created with the old Tails version are present in the filesystem 1.340
And all persistent directories from the old Tails version have safe access rights 2.590
After features/support/hooks.rb:291 0.706
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
7:59.814
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.424
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.049
And Tor is ready 20.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.231
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 2:15.839
Given I shutdown Tails and wait for the computer to power off 6.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.411
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.273
# 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.257
When the network is plugged 0.033
And Tor is ready 17.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.041
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.824
Given I shutdown Tails and wait for the computer to power off 4.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.579
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.933
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.039
And Tor is ready 18.733
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 14.682
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.014
After features/support/hooks.rb:291 0.714
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
34.395
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 9.547
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.527
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 18.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.361
After features/support/hooks.rb:291 0.725
After features/support/hooks.rb:75 0.000