Project Number Date
test_Tails_ISO_stable 5480 25 Feb 2025, 12:28

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:22.774 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.524
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.990
When I start Tails from USB drive "old" with network unplugged 1:28.965
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.098
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 7.143
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:28.512
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.893
And I take note of which tps features are available 1.349
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.289
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.847
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.010
When I write some files expected to persist 1.653
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.416
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.621
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.046
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.128
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.178
And I log in to a new session 19.062
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.506
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.735
Then the running Tails is installed on USB drive "to_upgrade" 18.782
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 3.582
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.437
Then all tps features from the old Tails version are active 1.760
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.515
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.671
After features/support/hooks.rb:330 1.224
After features/support/hooks.rb:100 0.009
6:41.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.834
And no SquashFS delta is installed 0.207
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.880
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.271
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.081
And Tor is ready 27.370
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.015
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.143
Given I shutdown Tails and wait for the computer to power off 10.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.107
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.364
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.372
When the network is plugged 0.076
And Tor is ready 19.806
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.906
Given I shutdown Tails and wait for the computer to power off 4.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.952
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.993
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.399
When the network is plugged 0.077
And Tor is ready 18.917
Then the Upgrader considers the system as up-to-date 0.312
# 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.863
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.928
After features/support/hooks.rb:330 0.779
After features/support/hooks.rb:100 0.020
40.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.940
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.103
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 23.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.635
After features/support/hooks.rb:330 0.696
After features/support/hooks.rb:100 0.000