Project Number Date
test_Tails_ISO_stable 5628 06 May 2025, 19:37

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 21:26.226 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
3:12.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.556
And I create a 7200 MiB disk named "old" 0.278
And I plug USB drive "old" 1.104
And I write an old version of the Tails USB image to disk "old" 1:4.977
When I start Tails from USB drive "old" with network unplugged 2:1.008
Then the boot device has safe access rights 3.201
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 7.189
After features/support/hooks.rb:100 0.052
Tags: @product
2:16.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:31.359
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 33.225
And I take note of which tps features are available 2.121
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.657
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.017
Tags: @product
2:59.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.681
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.460
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 3.133
And I take note of which tps features are available 0.656
And I shutdown Tails and wait for the computer to power off 6.759
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.898
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
2:34.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.944
And I log in to a new session 18.765
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.946
Then the running Tails is installed on USB drive "to_upgrade" 24.054
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.433
After features/support/hooks.rb:330 2.348
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.898
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.390
Then all tps features from the old Tails version are active 1.932
And Tails is running from USB drive "to_upgrade" 0.416
And the boot device has safe access rights 3.622
And the expected persistent files created with the old Tails version are present in the filesystem 1.695
And all persistent directories from the old Tails version have safe access rights 2.766
After features/support/hooks.rb:330 1.452
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:3.046
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.923
And no SquashFS delta is installed 0.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.493
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.620
When the network is plugged 0.077
And Tor is ready 21.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.982
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.643
Given I shutdown Tails and wait for the computer to power off 8.536
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.187
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.821
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.415
# 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.353
When the network is plugged 0.081
And Tor is ready 19.206
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.829
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.273
Given I shutdown Tails and wait for the computer to power off 4.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.178
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.546
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.085
And Tor is ready 18.310
Then the Upgrader considers the system as up-to-date 10.976
# 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.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.827
After features/support/hooks.rb:330 1.184
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.755
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.704
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.189
After features/support/hooks.rb:330 0.725
After features/support/hooks.rb:100 0.000