Project Number Date
test_Tails_ISO_devel 3761 30 Mar 2025, 13:14

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 22:24.264 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:24.055
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.257
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.181
When I start Tails from USB drive "old" with network unplugged 1:46.929
Then the boot device has safe access rights 3.326
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.178
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:330 8.829
After features/support/hooks.rb:100 0.024
Tags: @product
2:14.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login 1:28.886
Then Tails is running from USB drive "old" 0.509
And I create a persistent partition 33.273
And I take note of which tps features are available 2.104
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.647
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.012
Tags: @product
3:15.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 1.450
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.636
Then Tails is running from USB drive "old" 2.736
And all tps features are active 3.822
When I write some files expected to persist 2.987
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 4.114
And I take note of which tps features are available 0.617
And I shutdown Tails and wait for the computer to power off 6.795
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.504
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.690
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 without a persistent partition and stopped at Tails Greeter's login screen 26.709
And I log in to a new session 21.276
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.906
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.750
Then the running Tails is installed on USB drive "to_upgrade" 25.994
And I unplug USB drive "to_upgrade" 0.322
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:330 0.893
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.114
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.036
Then all tps features from the old Tails version are active 1.815
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 6.141
And the expected persistent files created with the old Tails version are present in the filesystem 1.843
And all persistent directories from the old Tails version have safe access rights 2.743
After features/support/hooks.rb:330 1.750
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:20.441
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.880
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.664
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.171
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.090
And Tor is ready 24.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.498
Given I shutdown Tails and wait for the computer to power off 1:28.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.645
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.276
When the network is plugged 0.070
And Tor is ready 19.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.423
Given I shutdown Tails and wait for the computer to power off 6.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.341
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.090
And Tor is ready 18.484
Then the Upgrader considers the system as up-to-date 0.330
# 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.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.892
After features/support/hooks.rb:330 0.736
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.133
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.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the signing key used by the Upgrader is outdated 0.147
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 19.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.264
After features/support/hooks.rb:330 0.755
After features/support/hooks.rb:100 0.000