Project Number Date
test_Tails_ISO_stable 5166 10 Oct 2024, 08:46

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:56.219 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:2.609
Before features/support/hooks.rb:269 0.010
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 28.016
When I start Tails from USB drive "old" with network unplugged 1:29.155
Then the boot device has safe access rights 3.147
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.629
After features/support/hooks.rb:100 0.011
Tags: @product
2:0.650
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:17.855
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.832
And I take note of which tps features are available 1.419
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.228
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.359
Before features/support/hooks.rb:269 0.004
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.944
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.255
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.340
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.023
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.836
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 27.126
And I log in to a new session 19.809
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.680
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.187
Then the running Tails is installed on USB drive "to_upgrade" 29.121
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 1.709
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.628
Before features/support/hooks.rb:269 0.006
Given a computer 0.290
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.142
Then all tps features from the old Tails version are active 1.632
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 2.956
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 2.969
After features/support/hooks.rb:326 0.638
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:21.139
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 12.687
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.120
And Tor is ready 20.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.728
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.377
Given I shutdown Tails and wait for the computer to power off 10.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.233
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.544
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.429
# 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.265
When the network is plugged 0.066
And Tor is ready 19.920
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.019
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.321
Given I shutdown Tails and wait for the computer to power off 4.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.922
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.121
And Tor is ready 18.308
Then the Upgrader considers the system as up-to-date 0.298
# 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.534
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.961
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.994
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.457
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.150
And the signing key used by the Upgrader is outdated 0.859
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 18.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.475
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.000