Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 9 13 Mar 2025, 07:30

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.311 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
1:58.073
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.517
When I start Tails from USB drive "old" with network unplugged 1:21.430
Then the boot device has safe access rights 2.882
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 6.868
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.430
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:25.394
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 30.737
And I take note of which tps features are available 2.528
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 6.396
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.008
Tags: @product
3:0.730
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.379
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.962
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.086
When I write some files expected to persist 1.670
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.342
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.554
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.298
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.734
And I log in to a new session 18.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.715
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.576
Then the running Tails is installed on USB drive "to_upgrade" 21.112
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 2.365
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.389
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.313
Then all tps features from the old Tails version are active 2.025
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 3.349
And the expected persistent files created with the old Tails version are present in the filesystem 1.463
And all persistent directories from the old Tails version have safe access rights 2.628
After features/support/hooks.rb:330 1.289
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:44.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.020
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.471
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.069
And Tor is ready 23.961
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.677
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.824
Given I shutdown Tails and wait for the computer to power off 11.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.409
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.364
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.284
When the network is plugged 0.064
And Tor is ready 19.201
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.527
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.920
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.293
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.280
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.082
And Tor is ready 18.324
Then the Upgrader considers the system as up-to-date 0.364
# 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.826
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.152
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.816
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.141
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 19.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.317
After features/support/hooks.rb:330 1.135
After features/support/hooks.rb:100 0.000