Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 30 02 Apr 2025, 06: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:27.317 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:59.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.169
When I start Tails from USB drive "old" with network unplugged 1:24.990
Then the boot device has safe access rights 3.232
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.386
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.591
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:21.637
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 31.466
And I take note of which tps features are available 1.480
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.243
After features/support/hooks.rb:330 0.218
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.898
Then Tails is running from USB drive "old" 0.484
And all tps features are active 2.022
When I write some files expected to persist 1.807
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.379
And all persistence configuration files have safe access rights 0.628
And all persistent directories from the old Tails version have safe access rights 2.693
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.380
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.560
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.999
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 9.984
And I log in to a new session 19.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.546
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.523
Then the running Tails is installed on USB drive "to_upgrade" 20.925
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:330 0.914
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.645
Then all tps features from the old Tails version are active 1.713
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.420
After features/support/hooks.rb:330 1.415
After features/support/hooks.rb:100 0.009
6:54.354
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 14.450
And no SquashFS delta is installed 0.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.081
And Tor is ready 27.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.476
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.886
Given I shutdown Tails and wait for the computer to power off 8.578
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.209
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 3.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.271
When the network is plugged 0.064
And Tor is ready 19.926
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.919
Given I shutdown Tails and wait for the computer to power off 6.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.786
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.592
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.086
And Tor is ready 19.898
Then the Upgrader considers the system as up-to-date 0.313
# 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.390
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.624
After features/support/hooks.rb:330 0.793
After features/support/hooks.rb:100 0.017
44.205
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.550
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 25.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.844
After features/support/hooks.rb:330 0.839
After features/support/hooks.rb:100 0.000