Project Number Date
test_Tails_ISO_devel 3785 17 Apr 2025, 23:42

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:35.125 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:13.690
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 33.118
When I start Tails from USB drive "old" with network unplugged 1:34.811
Then the boot device has safe access rights 3.290
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:330 3.741
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.776
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:25.633
Then Tails is running from USB drive "old" 0.439
And I create a persistent partition 31.463
And I take note of which tps features are available 1.817
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.391
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
3:0.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.953
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.064
When I write some files expected to persist 1.835
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.764
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.592
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.536
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.015
Tags: @product
2:43.386
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 12.313
And I log in to a new session 24.819
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.954
And I plug USB drive "to_upgrade" 2.523
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.453
Then the running Tails is installed on USB drive "to_upgrade" 22.881
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 7.155
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.431
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:15.296
Then all tps features from the old Tails version are active 1.836
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.695
And the expected persistent files created with the old Tails version are present in the filesystem 1.465
And all persistent directories from the old Tails version have safe access rights 2.504
After features/support/hooks.rb:330 1.564
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:18.941
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 12.525
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.470
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.073
And Tor is ready 24.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.835
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.999
Given I shutdown Tails and wait for the computer to power off 11.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.026
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.772
And the file system changes introduced in version 6.2~testoverlayfs are present 0.410
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.433
# 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.346
When the network is plugged 0.096
And Tor is ready 19.047
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.215
Given I shutdown Tails and wait for the computer to power off 4.604
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.110
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.854
And the file system changes introduced in version 6.3~testoverlayfs are present 0.824
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.488
When the network is plugged 0.290
And Tor is ready 19.725
Then the Upgrader considers the system as up-to-date 0.356
# 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 17.934
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.453
After features/support/hooks.rb:330 0.818
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
44.412
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.149
And the signing key used by the Upgrader is outdated 0.145
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 20.946
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.788
After features/support/hooks.rb:330 1.334
After features/support/hooks.rb:100 0.000