Project Number Date
test_Tails_ISO_devel 3795 29 Apr 2025, 19:16

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:58.526 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:30.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 35.924
When I start Tails from USB drive "old" with network unplugged 1:48.680
Then the boot device has safe access rights 3.236
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 10.341
After features/support/hooks.rb:100 0.026
Tags: @product
2:12.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:28.056
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 31.966
And I take note of which tps features are available 2.506
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 8.917
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.468
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.397
Then Tails is running from USB drive "old" 0.384
And all tps features are active 1.793
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.821
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 6.701
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.364
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.012
Tags: @product
2:36.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.797
And I log in to a new session 21.368
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.450
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.937
Then the running Tails is installed on USB drive "to_upgrade" 23.968
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.443
Then all tps features from the old Tails version are active 1.694
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.228
And the expected persistent files created with the old Tails version are present in the filesystem 1.364
And all persistent directories from the old Tails version have safe access rights 2.781
After features/support/hooks.rb:330 1.933
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:47.389
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 11.917
And no SquashFS delta is installed 0.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.489
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.548
When the network is plugged 0.161
And Tor is ready 24.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.173
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.526
Given I shutdown Tails and wait for the computer to power off 10.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.204
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 4.869
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.284
When the network is plugged 0.072
And Tor is ready 19.032
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.905
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.517
Given I shutdown Tails and wait for the computer to power off 4.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.335
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.224
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.068
And Tor is ready 18.360
Then the Upgrader considers the system as up-to-date 0.339
# 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.628
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.959
After features/support/hooks.rb:330 0.987
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
43.059
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.361
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.676
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 23.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.335
After features/support/hooks.rb:330 2.515
After features/support/hooks.rb:100 0.000