Project Number Date
test_Tails_ISO_devel 3614 17 Dec 2024, 12:38

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 19:8.994 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:18.706
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 29.699
When I start Tails from USB drive "old" with network unplugged 1:43.699
Then the boot device has safe access rights 3.027
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 7.023
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.368
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:22.023
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.726
And I take note of which tps features are available 1.516
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.674
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.626
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.101
Then Tails is running from USB drive "old" 0.312
And all tps features are active 2.298
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.394
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.130
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.497
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.768
And I log in to a new session 21.997
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.611
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.166
Then the running Tails is installed on USB drive "to_upgrade" 25.027
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:326 1.979
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.395
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.165
Then all tps features from the old Tails version are active 1.543
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.220
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:326 0.636
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:19.005
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.213
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.444
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.075
And Tor is ready 19.401
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.121
Given I shutdown Tails and wait for the computer to power off 8.681
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.416
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.280
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.264
When the network is plugged 0.074
And Tor is ready 18.289
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.553
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.148
Given I shutdown Tails and wait for the computer to power off 4.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.182
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.072
And Tor is ready 20.348
Then the Upgrader considers the system as up-to-date 0.301
# 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 15.279
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.127
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.394
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.864
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.890
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.598
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.000