Project Number Date
test_Tails_ISO_stable 4973 25 Jul 2024, 12:42

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:35.029 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:14.920
Before features/support/hooks.rb:269 0.028
Given a computer 0.282
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.910
When I start Tails from USB drive "old" with network unplugged 1:38.300
Then the boot device has safe access rights 3.215
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.020
Before features/support/hooks.rb:269 0.010
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:27.119
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 35.812
And I take note of which tps features are available 2.005
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 6.596
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.018
Tags: @product
2:49.760
Before features/support/hooks.rb:269 0.017
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.849
Then Tails is running from USB drive "old" 0.500
And all tps features are active 2.838
When I write some files expected to persist 1.768
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.862
And I take note of which tps features are available 0.673
And I shutdown Tails and wait for the computer to power off 4.367
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.043
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.143
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.836
And I log in to a new session 19.599
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.449
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.766
Then the running Tails is installed on USB drive "to_upgrade" 21.592
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:326 3.568
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.514
Before features/support/hooks.rb:269 0.008
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.251
Then all tps features from the old Tails version are active 1.687
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.748
And the expected persistent files created with the old Tails version are present in the filesystem 1.436
And all persistent directories from the old Tails version have safe access rights 2.802
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:29.872
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 12.273
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.629
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.039
And Tor is ready 24.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.201
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.723
Given I shutdown Tails and wait for the computer to power off 8.876
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.536
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.193
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.431
# 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.344
When the network is plugged 0.064
And Tor is ready 18.239
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.771
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.632
Given I shutdown Tails and wait for the computer to power off 4.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.751
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.349
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.039
And Tor is ready 19.029
Then the Upgrader considers the system as up-to-date 0.293
# 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.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:326 0.858
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.796
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.978
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.827
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 19.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.247
After features/support/hooks.rb:326 0.824
After features/support/hooks.rb:100 0.000