Project Number Date
test_Tails_ISO_improved-new-identity-scenario 13 12 May 2025, 13: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 22:8.733 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:15.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.081
And I write an old version of the Tails USB image to disk "old" 33.575
When I start Tails from USB drive "old" with network unplugged 1:35.463
Then the boot device has safe access rights 3.857
And Tails is running from USB drive "old" 0.436
And there is no persistence partition on USB drive "old" 0.104
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 3.777
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.546
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:31.514
Then Tails is running from USB drive "old" 0.586
And I create a persistent partition 33.820
And I take note of which tps features are available 1.734
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.842
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.425
Then Tails is running from USB drive "old" 0.693
And all tps features are active 4.201
When I write some files expected to persist 2.297
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.895
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 6.605
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.399
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.015
Tags: @product
2:46.260
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 10.892
And I log in to a new session 20.251
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.664
And I plug USB drive "to_upgrade" 2.509
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.571
Then the running Tails is installed on USB drive "to_upgrade" 30.806
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.323
After features/support/hooks.rb:330 3.224
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.316
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.845
Then all tps features from the old Tails version are active 2.052
And Tails is running from USB drive "to_upgrade" 0.443
And the boot device has safe access rights 4.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.961
After features/support/hooks.rb:330 0.821
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:24.621
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 11.296
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
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.574
When the network is plugged 0.080
And Tor is ready 22.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.894
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.724
Given I shutdown Tails and wait for the computer to power off 1:35.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.919
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.512
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.315
When the network is plugged 0.067
And Tor is ready 19.453
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.499
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.220
Given I shutdown Tails and wait for the computer to power off 5.050
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.414
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.247
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.120
And Tor is ready 18.271
Then the Upgrader considers the system as up-to-date 0.332
# 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.391
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.744
After features/support/hooks.rb:330 0.889
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.041
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 with a persistent partition enabled and logged in 9.672
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 22.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.631
After features/support/hooks.rb:330 1.169
After features/support/hooks.rb:100 0.000