Project Number Date
test_Tails_ISO_stable 4856 28 May 2024, 14:01

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:12.741 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:58.263
Before features/support/hooks.rb:259 0.005
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 33.047
When I start Tails from USB drive "old" with network unplugged 1:19.984
Then the boot device has safe access rights 2.949
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:305 3.535
After features/support/hooks.rb:89 0.012
Tags: @product
2:15.850
Before features/support/hooks.rb:259 0.008
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:27.423
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 36.128
And I take note of which tps features are available 1.786
Then a Tails persistence partition exists on USB drive "old" 1.325
And I shutdown Tails and wait for the computer to power off 8.712
After features/support/hooks.rb:305 0.204
After features/support/hooks.rb:89 0.010
Tags: @product
2:48.221
Before features/support/hooks.rb:259 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.339
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.016
When I write some files expected to persist 1.760
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.386
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 4.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.685
After features/support/hooks.rb:305 0.111
After features/support/hooks.rb:89 0.010
Tags: @product
2:47.167
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 24.520
And I log in to a new session 18.555
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.213
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.842
Then the running Tails is installed on USB drive "to_upgrade" 23.214
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:305 2.008
After features/support/hooks.rb:89 0.000
Tags: @product
2:8.671
Before features/support/hooks.rb:259 0.008
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.461
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.153
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.365
After features/support/hooks.rb:305 0.650
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:37.248
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.298
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.037
And Tor is ready 19.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.736
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.223
Given I shutdown Tails and wait for the computer to power off 8.753
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.209
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
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.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.269
When the network is plugged 0.043
And Tor is ready 19.084
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.433
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.138
Given I shutdown Tails and wait for the computer to power off 4.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.700
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 3.812
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.416
When the network is plugged 0.033
And Tor is ready 48.016
Then the Upgrader considers the system as up-to-date 0.306
# 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.865
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.970
After features/support/hooks.rb:305 0.746
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
37.318
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 10.239
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.045
And Tor is ready 18.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.894
After features/support/hooks.rb:305 0.684
After features/support/hooks.rb:89 0.000