Project Number Date
test_Tails_ISO_devel 3758 27 Mar 2025, 14:24

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 23:42.081 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:35.178
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.488
When I start Tails from USB drive "old" with network unplugged 1:57.422
Then the boot device has safe access rights 3.765
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.404
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 3.787
After features/support/hooks.rb:100 0.021
Tags: @product
2:26.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:39.792
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 34.541
And I take note of which tps features are available 1.894
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 9.038
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.010
Tags: @product
3:44.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:57.576
Then Tails is running from USB drive "old" 0.461
And all tps features are active 2.783
When I write some files expected to persist 2.209
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.336
And all persistence configuration files have safe access rights 0.742
And all persistent directories from the old Tails version have safe access rights 3.238
And I take note of which tps features are available 0.630
And I shutdown Tails and wait for the computer to power off 6.549
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.149
After features/support/hooks.rb:330 0.232
After features/support/hooks.rb:100 0.037
Tags: @product
3:6.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.139
And I log in to a new session 24.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.002
And I plug USB drive "to_upgrade" 2.643
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.189
Then the running Tails is installed on USB drive "to_upgrade" 34.806
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 2.846
After features/support/hooks.rb:100 0.000
Tags: @product
2:51.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:40.106
Then all tps features from the old Tails version are active 2.196
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.702
And the expected persistent files created with the old Tails version are present in the filesystem 1.620
And all persistent directories from the old Tails version have safe access rights 3.172
After features/support/hooks.rb:330 1.800
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:13.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 35.178
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.602
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.581
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.086
And Tor is ready 23.720
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.762
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.195
Given I shutdown Tails and wait for the computer to power off 14.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.195
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 6.741
And the file system changes introduced in version 6.2~testoverlayfs are present 0.473
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.525
# 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.468
When the network is plugged 0.413
And Tor is ready 19.870
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.246
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.790
Given I shutdown Tails and wait for the computer to power off 7.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.474
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.637
And the file system changes introduced in version 6.3~testoverlayfs are present 0.633
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.441
When the network is plugged 0.117
And Tor is ready 21.562
Then the Upgrader considers the system as up-to-date 0.372
# 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 20.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.178
After features/support/hooks.rb:330 0.966
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
44.170
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.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.134
And the signing key used by the Upgrader is outdated 0.187
But a current signing key is available on our website 0.000
When the network is plugged 0.161
And Tor is ready 22.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.928
After features/support/hooks.rb:330 2.119
After features/support/hooks.rb:100 0.000