Project Number Date
test_Tails_ISO_stable 5524 20 Mar 2025, 23:02

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 18:54.831 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:4.243
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 28.218
When I start Tails from USB drive "old" with network unplugged 1:30.640
Then the boot device has safe access rights 3.124
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 3.549
After features/support/hooks.rb:100 0.051
Tags: @product
2:7.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:23.958
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 32.784
And I take note of which tps features are available 1.464
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 8.291
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.723
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.883
When I write some files expected to persist 1.652
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.255
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.714
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.638
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.569
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 22.963
And I log in to a new session 18.055
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.906
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.383
Then the running Tails is installed on USB drive "to_upgrade" 21.440
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 6.695
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.427
Then all tps features from the old Tails version are active 1.667
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.243
And the expected persistent files created with the old Tails version are present in the filesystem 1.395
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:330 1.268
After features/support/hooks.rb:100 0.009
6:18.110
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.944
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.125
And Tor is ready 19.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.656
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.257
Given I shutdown Tails and wait for the computer to power off 8.783
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.906
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.909
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.241
When the network is plugged 0.073
And Tor is ready 21.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.844
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.434
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.829
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.872
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.063
And Tor is ready 17.103
Then the Upgrader considers the system as up-to-date 0.317
# 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.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.976
After features/support/hooks.rb:330 0.684
After features/support/hooks.rb:100 0.018
36.819
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 9.949
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.156
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.714
After features/support/hooks.rb:330 0.665
After features/support/hooks.rb:100 0.000