Project Number Date
test_Tails_ISO_devel 4062 09 Nov 2025, 12:11

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 15:31.563 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
1:46.511
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 32.576
When I start Tails from USB drive "old" with network unplugged 1:9.102
Then the boot device has safe access rights 2.728
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:331 3.738
After features/support/hooks.rb:100 0.014
Tags: @product
2:3.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:24.568
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 28.881
And I take note of which tps features are available 1.149
Then a Tails persistence partition exists on USB drive "old" 0.648
And I shutdown Tails and wait for the computer to power off 7.950
After features/support/hooks.rb:331 0.309
After features/support/hooks.rb:100 0.010
Tags: @product
2:2.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.437
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.821
When I write some files expected to persist 1.411
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.694
And all persistent directories from the old Tails version have safe access rights 2.308
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 3.468
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.942
After features/support/hooks.rb:331 0.313
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.774
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 12.460
And I log in to a new session 16.650
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.752
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.407
Then the running Tails is installed on USB drive "to_upgrade" 20.661
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:331 3.799
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.842
Then all tps features from the old Tails version are active 1.651
And Tails is running from USB drive "to_upgrade" 0.467
And the boot device has safe access rights 3.120
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 2.362
After features/support/hooks.rb:331 0.872
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:53.927
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.077
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
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.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.095
And Tor is ready 13.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.855
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.849
Given I shutdown Tails and wait for the computer to power off 10.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.635
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.952
And the file system changes introduced in version 6.2~testoverlayfs are present 0.262
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.147
# 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.278
When the network is plugged 0.055
And Tor is ready 13.080
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.599
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.579
Given I shutdown Tails and wait for the computer to power off 8.040
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.617
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.149
And Tor is ready 10.729
Then the Upgrader considers the system as up-to-date 0.179
# 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 5.556
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.500
After features/support/hooks.rb:331 0.892
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
26.396
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 12.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.884
After features/support/hooks.rb:331 1.009
After features/support/hooks.rb:100 0.000