Project Number Date
test_Tails_ISO_stable 4914 27 Jun 2024, 13:13

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 20:26.786 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:39.544
Before features/support/hooks.rb:269 0.018
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.454
When I start Tails from USB drive "old" with network unplugged 2:2.415
Then the boot device has safe access rights 3.291
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.098
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 7.204
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.102
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:28.426
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 32.683
And I take note of which tps features are available 2.174
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 8.416
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.622
Before features/support/hooks.rb:269 0.007
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.303
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.409
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.524
And all persistent directories from the old Tails version have safe access rights 2.614
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.238
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.493
After features/support/hooks.rb:326 0.106
After features/support/hooks.rb:100 0.012
Tags: @product
2:25.927
Before features/support/hooks.rb:269 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 11.113
And I log in to a new session 17.277
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.233
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.811
Then the running Tails is installed on USB drive "to_upgrade" 19.656
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.557
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.145
Before features/support/hooks.rb:269 0.009
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.479
Then all tps features from the old Tails version are active 2.366
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.328
And the expected persistent files created with the old Tails version are present in the filesystem 1.876
And all persistent directories from the old Tails version have safe access rights 2.538
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:34.284
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.858
And no SquashFS delta is installed 0.095
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.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.055
And Tor is ready 21.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.872
Given I shutdown Tails and wait for the computer to power off 1:7.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.394
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.436
# 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.389
When the network is plugged 0.041
And Tor is ready 18.217
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.998
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.226
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.046
And Tor is ready 18.728
Then the Upgrader considers the system as up-to-date 10.766
# 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 15.355
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.898
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.159
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.979
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.818
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 16.420
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.555
After features/support/hooks.rb:326 0.798
After features/support/hooks.rb:100 0.000