Project Number Date
test_Tails_ISO_stable 4815 29 Apr 2024, 12:30

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:10.713 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:7.382
Before features/support/hooks.rb:259 0.004
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.093
And I write an old version of the Tails USB image to disk "old" 29.885
When I start Tails from USB drive "old" with network unplugged 1:32.118
Then the boot device has safe access rights 3.015
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:305 3.629
After features/support/hooks.rb:89 0.071
Tags: @product
2:20.188
Before features/support/hooks.rb:259 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:31.782
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 35.126
And I take note of which tps features are available 1.866
Then a Tails persistence partition exists on USB drive "old" 2.344
And I shutdown Tails and wait for the computer to power off 8.504
After features/support/hooks.rb:305 0.144
After features/support/hooks.rb:89 0.011
Tags: @product
2:51.781
Before features/support/hooks.rb:259 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.461
Then Tails is running from USB drive "old" 0.365
And all tps features are active 2.119
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.797
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.386
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.569
After features/support/hooks.rb:305 0.168
After features/support/hooks.rb:89 0.009
Tags: @product
2:29.596
Before features/support/hooks.rb:259 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.746
And I log in to a new session 22.175
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.613
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.186
Then the running Tails is installed on USB drive "to_upgrade" 15.136
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 2.156
After features/support/hooks.rb:89 0.000
Tags: @product
2:14.838
Before features/support/hooks.rb:259 0.008
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.427
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.577
And the expected persistent files created with the old Tails version are present in the filesystem 1.322
And all persistent directories from the old Tails version have safe access rights 2.338
After features/support/hooks.rb:305 0.714
After features/support/hooks.rb:89 0.010
6:31.308
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.039
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
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.439
When the network is plugged 0.040
And Tor is ready 21.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.237
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.091
Given I shutdown Tails and wait for the computer to power off 8.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.706
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.314
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
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.318
# 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.268
When the network is plugged 0.043
And Tor is ready 19.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.373
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.555
Given I shutdown Tails and wait for the computer to power off 4.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.215
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.053
And Tor is ready 20.966
Then the Upgrader considers the system as up-to-date 0.298
# 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 16.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:305 0.744
After features/support/hooks.rb:89 0.023
35.616
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.919
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.062
And the signing key used by the Upgrader is outdated 0.785
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 19.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.077
After features/support/hooks.rb:305 0.681
After features/support/hooks.rb:89 0.000