Project Number Date
test_Tails_ISO_improved-new-identity-scenario 4 03 May 2025, 12: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 18:46.381 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.200
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.712
When I start Tails from USB drive "old" with network unplugged 1:29.348
Then the boot device has safe access rights 2.880
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.547
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:25.043
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.539
And I take note of which tps features are available 1.801
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.175
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.387
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.259
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.904
When I write some files expected to persist 1.972
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.236
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 4.604
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.865
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.113
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 without a persistent partition and stopped at Tails Greeter's login screen 9.967
And I log in to a new session 17.703
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.385
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.455
Then the running Tails is installed on USB drive "to_upgrade" 20.768
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 1.870
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.631
Then all tps features from the old Tails version are active 1.639
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.317
And the expected persistent files created with the old Tails version are present in the filesystem 1.334
And all persistent directories from the old Tails version have safe access rights 2.314
After features/support/hooks.rb:330 1.308
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.860
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 11.788
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.070
And Tor is ready 21.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.937
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.847
Given I shutdown Tails and wait for the computer to power off 8.493
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.555
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.177
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
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.304
# 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.320
When the network is plugged 0.065
And Tor is ready 16.821
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.147
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.451
Given I shutdown Tails and wait for the computer to power off 6.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.405
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.083
And Tor is ready 15.768
Then the Upgrader considers the system as up-to-date 10.743
# 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.962
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.596
After features/support/hooks.rb:330 0.744
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
40.171
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.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 21.152
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.948
After features/support/hooks.rb:330 1.199
After features/support/hooks.rb:100 0.000