Project Number Date
test_Tails_ISO_stable 5711 11 Jun 2025, 20: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 20:58.509 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:19.985
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.895
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.944
When I start Tails from USB drive "old" with network unplugged 1:40.256
Then the boot device has safe access rights 3.679
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.798
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:29.403
Then Tails is running from USB drive "old" 0.423
And I create a persistent partition 32.218
And I take note of which tps features are available 2.855
Then a Tails persistence partition exists on USB drive "old" 0.956
And I shutdown Tails and wait for the computer to power off 8.764
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.008
Tags: @product
3:17.647
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.033
Then Tails is running from USB drive "old" 0.316
And all tps features are active 5.061
When I write some files expected to persist 2.175
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.617
And I take note of which tps features are available 0.863
And I shutdown Tails and wait for the computer to power off 6.600
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.963
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.022
Tags: @product
2:48.502
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 without a persistent partition and stopped at Tails Greeter's login screen 15.699
And I log in to a new session 22.164
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.160
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.786
Then the running Tails is installed on USB drive "to_upgrade" 28.735
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 6.923
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.648
Then all tps features from the old Tails version are active 1.843
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.988
And the expected persistent files created with the old Tails version are present in the filesystem 1.558
And all persistent directories from the old Tails version have safe access rights 2.751
After features/support/hooks.rb:330 1.724
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:5.486
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 with a persistent partition enabled and logged in 15.042
And no SquashFS delta is installed 0.223
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.076
And Tor is ready 25.586
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.813
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.420
Given I shutdown Tails and wait for the computer to power off 11.163
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.783
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.606
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.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.432
When the network is plugged 0.070
And Tor is ready 19.629
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.408
Given I shutdown Tails and wait for the computer to power off 6.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.118
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.499
And the file system changes introduced in version 6.3~testoverlayfs are present 0.623
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.549
When the network is plugged 0.097
And Tor is ready 17.334
Then the Upgrader considers the system as up-to-date 0.318
# 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.606
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.562
After features/support/hooks.rb:330 0.706
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.643
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 with a persistent partition enabled and logged in 10.535
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.690
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.002
After features/support/hooks.rb:330 1.040
After features/support/hooks.rb:100 0.000