Project Number Date
test_Tails_ISO_devel 3426 14 Jun 2024, 13: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 21:47.147 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:9.579
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 30.385
When I start Tails from USB drive "old" with network unplugged 1:33.996
Then the boot device has safe access rights 2.858
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:315 3.569
After features/support/hooks.rb:100 0.026
Tags: @product
2:12.078
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:25.100
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 35.338
And I take note of which tps features are available 1.806
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.378
After features/support/hooks.rb:315 0.160
After features/support/hooks.rb:100 0.025
Tags: @product
2:52.549
Before features/support/hooks.rb:269 0.018
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.028
Then Tails is running from USB drive "old" 0.347
And all tps features are active 2.238
When I write some files expected to persist 1.882
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.979
And I take note of which tps features are available 0.520
And I shutdown Tails and wait for the computer to power off 4.496
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.137
After features/support/hooks.rb:315 0.133
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.024
Before features/support/hooks.rb:269 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 11.773
And I log in to a new session 20.797
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.655
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.409
Then the running Tails is installed on USB drive "to_upgrade" 22.520
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:315 2.389
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.920
Before features/support/hooks.rb:269 0.008
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.753
Then all tps features from the old Tails version are active 2.107
And Tails is running from USB drive "to_upgrade" 0.583
And the boot device has safe access rights 3.775
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 2.852
After features/support/hooks.rb:315 0.781
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:45.814
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.502
And no SquashFS delta is installed 0.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
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.410
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.605
When the network is plugged 0.140
And Tor is ready 19.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.996
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.740
Given I shutdown Tails and wait for the computer to power off 1:23.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.797
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.550
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.310
When the network is plugged 0.067
And Tor is ready 20.458
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.149
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.568
Given I shutdown Tails and wait for the computer to power off 4.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.943
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.240
And the file system changes introduced in version 6.3~testoverlayfs are present 0.572
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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.334
When the network is plugged 0.043
And Tor is ready 48.099
Then the Upgrader considers the system as up-to-date 0.341
# 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.535
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.088
After features/support/hooks.rb:315 0.746
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.181
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.643
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
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 1.618
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 18.029
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.424
After features/support/hooks.rb:315 1.095
After features/support/hooks.rb:100 0.000