Project Number Date
test_Tails_ISO_devel 3634 06 Jan 2025, 12:26

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:49.404 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:16.257
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 29.812
When I start Tails from USB drive "old" with network unplugged 1:41.352
Then the boot device has safe access rights 2.857
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.743
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.897
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:26.378
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 32.917
And I take note of which tps features are available 1.933
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 8.344
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.691
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.178
Then Tails is running from USB drive "old" 0.639
And all tps features are active 2.015
When I write some files expected to persist 1.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
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.552
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.336
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.096
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.281
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.558
And I log in to a new session 18.311
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.577
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.352
Then the running Tails is installed on USB drive "to_upgrade" 21.705
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.357
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.069
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.549
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.117
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.825
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:16.190
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.963
And no SquashFS delta is installed 0.523
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.548
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.067
And Tor is ready 23.349
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.457
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.680
Given I shutdown Tails and wait for the computer to power off 10.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.967
Then Tails is running version 6.2~testoverlayfs 0.034
And all tps features are active 2.132
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.267
When the network is plugged 0.083
And Tor is ready 18.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.269
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.781
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.819
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.376
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.061
And Tor is ready 17.625
Then the Upgrader considers the system as up-to-date 0.302
# 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.425
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.016
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.766
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.802
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 19.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.467
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.000