Project Number Date
test_Tails_ISO_devel 3648 15 Jan 2025, 17:54

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:2.275 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:6.547
Before features/support/hooks.rb:269 0.003
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 33.579
When I start Tails from USB drive "old" with network unplugged 1:27.711
Then the boot device has safe access rights 3.001
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 0.873
After features/support/hooks.rb:100 0.023
Tags: @product
2:11.116
Before features/support/hooks.rb:269 0.002
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:23.370
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 36.104
And I take note of which tps features are available 1.666
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.598
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.006
Tags: @product
2:53.101
Before features/support/hooks.rb:269 0.003
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.800
Then Tails is running from USB drive "old" 1.311
And all tps features are active 2.020
When I write some files expected to persist 1.594
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 3.269
And I take note of which tps features are available 0.664
And I shutdown Tails and wait for the computer to power off 6.223
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.322
After features/support/hooks.rb:326 0.094
After features/support/hooks.rb:100 0.006
Tags: @product
2:21.231
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.738
And I log in to a new session 18.070
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.432
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.403
Then the running Tails is installed on USB drive "to_upgrade" 17.784
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 6.742
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.468
Before features/support/hooks.rb:269 0.003
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.936
Then all tps features from the old Tails version are active 1.572
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.533
After features/support/hooks.rb:326 0.618
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:31.871
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.754
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.085
And Tor is ready 22.506
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.104
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.919
Given I shutdown Tails and wait for the computer to power off 11.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.897
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.403
And only the 6.2~testoverlayfs SquashFS delta is installed 0.116
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.480
# 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.351
When the network is plugged 0.084
And Tor is ready 19.122
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.177
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.406
Given I shutdown Tails and wait for the computer to power off 4.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.059
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.178
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.069
And Tor is ready 17.933
Then the Upgrader considers the system as up-to-date 0.386
# 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.939
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.874
After features/support/hooks.rb:326 0.650
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
39.939
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.950
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.418
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.000