Project Number Date
test_Tails_ISO_stable 5061 31 Aug 2024, 12: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 18:19.657 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:4.313
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.893
When I start Tails from USB drive "old" with network unplugged 1:28.178
Then the boot device has safe access rights 3.027
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 9.297
After features/support/hooks.rb:100 0.008
Tags: @product
1:59.711
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:18.086
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 30.689
And I take note of which tps features are available 1.456
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.146
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.213
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.081
Then Tails is running from USB drive "old" 0.290
And all tps features are active 1.906
When I write some files expected to persist 1.633
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.258
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.342
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.801
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.967
And I log in to a new session 17.954
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.942
And I plug USB drive "to_upgrade" 2.369
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.503
Then the running Tails is installed on USB drive "to_upgrade" 16.668
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.629
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.854
Before features/support/hooks.rb:269 0.005
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.246
Then all tps features from the old Tails version are active 1.497
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.341
And all persistent directories from the old Tails version have safe access rights 2.206
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:16.209
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 11.012
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
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.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.066
And Tor is ready 21.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.898
Given I shutdown Tails and wait for the computer to power off 8.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.266
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.965
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.242
When the network is plugged 0.073
And Tor is ready 18.259
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.335
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.615
Given I shutdown Tails and wait for the computer to power off 4.601
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.726
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.042
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.071
And Tor is ready 16.924
Then the Upgrader considers the system as up-to-date 0.353
# 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.997
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.031
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
36.553
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 9.947
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.797
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 19.029
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.372
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000