Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 2 05 Mar 2025, 07:06

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:52.253 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.013
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.809
When I start Tails from USB drive "old" with network unplugged 1:22.865
Then the boot device has safe access rights 3.105
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.487
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:31.325
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 32.578
And I take note of which tps features are available 1.355
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.208
After features/support/hooks.rb:330 0.265
After features/support/hooks.rb:100 0.014
Tags: @product
2:50.520
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.322
Then Tails is running from USB drive "old" 0.454
And all tps features are active 1.834
When I write some files expected to persist 1.679
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 3.092
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 4.430
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.537
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.934
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 without a persistent partition and stopped at Tails Greeter's login screen 9.883
And I log in to a new session 17.788
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.636
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.139
Then the running Tails is installed on USB drive "to_upgrade" 17.619
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 2.625
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.324
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.234
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.231
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.333
After features/support/hooks.rb:330 1.241
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.206
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 10.979
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.068
And Tor is ready 20.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.430
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.488
Given I shutdown Tails and wait for the computer to power off 8.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.234
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.164
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.079
And Tor is ready 47.146
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.082
Given I shutdown Tails and wait for the computer to power off 4.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.503
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.958
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.075
And Tor is ready 20.128
Then the Upgrader considers the system as up-to-date 0.332
# 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.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.056
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.426
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 9.486
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.532
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.720
After features/support/hooks.rb:330 0.849
After features/support/hooks.rb:100 0.000