Project Number Date
test_Tails_ISO_devel 3316 11 Mar 2024, 15:03

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:19.296 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
1:42.412
Before features/support/hooks.rb:245 0.008
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 21.260
When I start Tails from USB drive "old" with network unplugged 1:15.843
Then the boot device has safe access rights 3.055
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 8.319
After features/support/hooks.rb:75 0.010
Tags: @product
2:7.020
Before features/support/hooks.rb:245 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:15.268
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 41.299
And I take note of which tps features are available 1.897
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 7.247
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.011
Tags: @product
2:46.546
Before features/support/hooks.rb:245 0.007
Given a computer 1.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.565
Then Tails is running from USB drive "old" 0.421
And all tps features are active 2.087
When I write some files expected to persist 1.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.338
And I take note of which tps features are available 0.397
And I shutdown Tails and wait for the computer to power off 4.155
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.893
After features/support/hooks.rb:291 0.131
After features/support/hooks.rb:75 0.009
Tags: @product
2:34.158
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.014
And I log in to a new session 17.300
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.652
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.442
Then the running Tails is installed on USB drive "to_upgrade" 13.832
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 3.741
After features/support/hooks.rb:75 0.000
Tags: @product
2:23.766
Before features/support/hooks.rb:245 0.009
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.557
Then all tps features from the old Tails version are active 1.526
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.224
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.392
After features/support/hooks.rb:291 0.575
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
7:12.317
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.819
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.037
And Tor is ready 45.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.803
Given I shutdown Tails and wait for the computer to power off 6.203
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.304
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.020
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.319
When the network is plugged 0.033
And Tor is ready 17.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.400
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.949
Given I shutdown Tails and wait for the computer to power off 4.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.012
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.994
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.047
And Tor is ready 13.464
Then the Upgrader considers the system as up-to-date 10.643
# 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 12.529
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.081
After features/support/hooks.rb:291 0.999
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
33.073
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.600
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 15.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.679
After features/support/hooks.rb:291 0.925
After features/support/hooks.rb:75 0.000