Project Number Date
test_Tails_ISO_stable 4957 19 Jul 2024, 12:19

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:12.060 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.616
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.097
When I start Tails from USB drive "old" with network unplugged 1:27.250
Then the boot device has safe access rights 2.949
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 7.341
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.908
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:19.648
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 31.068
And I take note of which tps features are available 1.471
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 8.299
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.527
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.024
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.858
When I write some files expected to persist 1.494
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.418
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.271
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.935
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.213
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 9.559
And I log in to a new session 17.762
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.259
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.294
Then the running Tails is installed on USB drive "to_upgrade" 19.584
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 1.851
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.624
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.644
Then all tps features from the old Tails version are active 1.577
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.199
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.248
After features/support/hooks.rb:326 0.609
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:9.084
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.696
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.071
And Tor is ready 19.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.455
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.275
Given I shutdown Tails and wait for the computer to power off 8.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.193
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.063
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
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.308
# 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.306
When the network is plugged 0.048
And Tor is ready 17.563
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.968
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.508
Given I shutdown Tails and wait for the computer to power off 4.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.079
Then Tails is running version 6.3~testoverlayfs 0.029
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.033
And Tor is ready 19.667
Then the Upgrader considers the system as up-to-date 0.318
# 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.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.194
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
34.085
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 9.536
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.762
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 15.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.888
After features/support/hooks.rb:326 0.764
After features/support/hooks.rb:100 0.000