Project Number Date
test_Tails_ISO_devel 3850 02 Jun 2025, 19:58

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 20:40.309 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:11.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.105
And I write an old version of the Tails USB image to disk "old" 33.656
When I start Tails from USB drive "old" with network unplugged 1:32.267
Then the boot device has safe access rights 3.254
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:330 3.843
After features/support/hooks.rb:100 0.011
Tags: @product
2:20.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:35.301
Then Tails is running from USB drive "old" 0.453
And I create a persistent partition 32.946
And I take note of which tps features are available 2.514
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 8.479
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.652
Then Tails is running from USB drive "old" 0.487
And all tps features are active 2.283
When I write some files expected to persist 1.878
# 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.421
And all persistent directories from the old Tails version have safe access rights 2.750
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.469
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.073
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.155
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 12.272
And I log in to a new session 23.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.664
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.797
Then the running Tails is installed on USB drive "to_upgrade" 29.221
And I unplug USB drive "to_upgrade" 0.262
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 3.657
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.350
Then all tps features from the old Tails version are active 1.964
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 4.012
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.619
After features/support/hooks.rb:330 1.111
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:12.386
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 with a persistent partition enabled and logged in 14.609
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.141
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.470
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.690
When the network is plugged 0.077
And Tor is ready 22.442
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.763
Given I shutdown Tails and wait for the computer to power off 11.209
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.809
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.301
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
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.326
# 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.262
When the network is plugged 0.088
And Tor is ready 21.099
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.001
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.711
Given I shutdown Tails and wait for the computer to power off 6.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.705
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.185
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.070
And Tor is ready 17.813
Then the Upgrader considers the system as up-to-date 10.853
# 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.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.525
After features/support/hooks.rb:330 0.748
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.360
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 with a persistent partition enabled and logged in 10.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 18.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.366
After features/support/hooks.rb:330 0.951
After features/support/hooks.rb:100 0.000