Project Number Date
test_Tails_ISO_devel 3778 11 Apr 2025, 13:42

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 20:45.453 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:26.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 32.461
When I start Tails from USB drive "old" with network unplugged 1:47.641
Then the boot device has safe access rights 3.812
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:330 7.191
After features/support/hooks.rb:100 0.013
Tags: @product
2:17.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login 1:29.960
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 36.956
And I take note of which tps features are available 2.499
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 6.777
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.015
Tags: @product
3:14.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.814
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.409
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.552
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.604
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.134
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.767
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 16.255
And I log in to a new session 20.661
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.179
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.178
Then the running Tails is installed on USB drive "to_upgrade" 26.620
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 7.029
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.336
Then all tps features from the old Tails version are active 2.225
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.879
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.743
After features/support/hooks.rb:330 1.584
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:53.539
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 15.043
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.409
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.076
And Tor is ready 22.509
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.535
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.815
Given I shutdown Tails and wait for the computer to power off 8.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.072
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.475
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.442
# 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.313
When the network is plugged 0.077
And Tor is ready 17.499
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.717
Given I shutdown Tails and wait for the computer to power off 4.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.996
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.073
And Tor is ready 19.534
Then the Upgrader considers the system as up-to-date 0.360
# 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.537
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
40.579
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 21.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.806
After features/support/hooks.rb:330 0.762
After features/support/hooks.rb:100 0.000