Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 3 06 Mar 2025, 06:23

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:37.911 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:19.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.398
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 35.546
When I start Tails from USB drive "old" with network unplugged 1:37.849
Then the boot device has safe access rights 3.419
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.520
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:31.145
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 32.473
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.578
After features/support/hooks.rb:330 0.267
After features/support/hooks.rb:100 0.013
Tags: @product
2:48.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.127
Then Tails is running from USB drive "old" 0.582
And all tps features are active 2.137
When I write some files expected to persist 1.767
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.944
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.472
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.288
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.097
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.374
And I log in to a new session 18.890
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.908
Then the running Tails is installed on USB drive "to_upgrade" 23.581
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 2.185
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.234
Then all tps features from the old Tails version are active 1.814
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.073
And the expected persistent files created with the old Tails version are present in the filesystem 1.503
And all persistent directories from the old Tails version have safe access rights 2.453
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
6:43.336
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 13.776
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.079
And Tor is ready 29.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.922
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.729
Given I shutdown Tails and wait for the computer to power off 8.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.134
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.446
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
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.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.280
When the network is plugged 0.100
And Tor is ready 17.880
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.105
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.048
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.998
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.307
And the file system changes introduced in version 6.3~testoverlayfs are present 0.600
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.096
And Tor is ready 16.736
Then the Upgrader considers the system as up-to-date 10.870
# 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 16.633
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.147
After features/support/hooks.rb:330 0.746
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
39.717
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.522
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.128
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 20.521
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.323
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.000