Project Number Date
test_Tails_ISO_devel 3754 26 Mar 2025, 13:19

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 19:17.867 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:6.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.722
When I start Tails from USB drive "old" with network unplugged 1:27.643
Then the boot device has safe access rights 3.504
And Tails is running from USB drive "old" 0.426
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:330 3.511
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:28.722
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 32.131
And I take note of which tps features are available 2.299
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.662
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.806
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.062
When I write some files expected to persist 2.046
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.378
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.349
# 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.169
After features/support/hooks.rb:100 0.013
Tags: @product
2:28.352
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 without a persistent partition and stopped at Tails Greeter's login screen 11.004
And I log in to a new session 18.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.957
Then the running Tails is installed on USB drive "to_upgrade" 18.448
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 2.627
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.851
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.640
Then all tps features from the old Tails version are active 1.835
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.762
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.552
After features/support/hooks.rb:330 1.888
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:30.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.546
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.462
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.070
And Tor is ready 19.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.394
Given I shutdown Tails and wait for the computer to power off 8.980
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.957
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.634
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.312
When the network is plugged 0.074
And Tor is ready 17.090
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.959
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.221
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.217
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.410
When the network is plugged 0.074
And Tor is ready 20.965
Then the Upgrader considers the system as up-to-date 0.340
# 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 15.219
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.450
After features/support/hooks.rb:330 0.867
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.871
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 9.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 19.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.652
After features/support/hooks.rb:330 1.144
After features/support/hooks.rb:100 0.000