Project Number Date
test_Tails_ISO_stable 4953 17 Jul 2024, 22:52

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:16.589 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:5.470
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 36.139
When I start Tails from USB drive "old" with network unplugged 1:24.141
Then the boot device has safe access rights 2.897
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 6.906
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.338
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:27.922
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.204
And I take note of which tps features are available 1.688
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.172
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.905
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.941
Then Tails is running from USB drive "old" 0.372
And all tps features are active 1.778
When I write some files expected to persist 1.537
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.582
And all persistent directories from the old Tails version have safe access rights 2.368
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.633
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.836
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.837
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 10.201
And I log in to a new session 17.245
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.240
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.346
Then the running Tails is installed on USB drive "to_upgrade" 17.975
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 6.691
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.384
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.547
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.075
And the expected persistent files created with the old Tails version are present in the filesystem 1.365
And all persistent directories from the old Tails version have safe access rights 2.262
After features/support/hooks.rb:326 0.844
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:10.821
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 10.586
And no SquashFS delta is installed 0.450
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.143
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.034
And Tor is ready 19.952
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.221
Given I shutdown Tails and wait for the computer to power off 8.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.981
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.261
When the network is plugged 0.034
And Tor is ready 18.894
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.469
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.010
Given I shutdown Tails and wait for the computer to power off 4.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.360
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.825
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.308
When the network is plugged 0.042
And Tor is ready 20.163
Then the Upgrader considers the system as up-to-date 0.306
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
35.831
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 9.653
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.714
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.084
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000