Project Number Date
test_Tails_ISO_devel 4184 22 Jan 2026, 18:01

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 13:53.705 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:43.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 37.475
When I start Tails from USB drive "old" with network unplugged 1:1.104
Then the boot device has safe access rights 3.301
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.897
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:2.580
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 28.555
And I take note of which tps features are available 1.221
Then a Tails persistence partition exists on USB drive "old" 0.662
And I shutdown Tails and wait for the computer to power off 7.759
After features/support/hooks.rb:331 0.217
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.663
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.044
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.855
When I write some files expected to persist 1.583
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.215
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 7.434
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.024
After features/support/hooks.rb:331 0.216
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.869
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 11.375
And I log in to a new session 13.645
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.722
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.168
Then the running Tails is installed on USB drive "to_upgrade" 21.836
And I unplug USB drive "to_upgrade" 0.529
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 3.933
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.318
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.565
Then all tps features from the old Tails version are active 1.381
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.097
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.364
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:17.231
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 12.046
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.061
And Tor is ready 13.558
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.650
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.136
Given I shutdown Tails and wait for the computer to power off 11.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.024
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.044
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.245
When the network is plugged 0.062
And Tor is ready 12.675
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.072
Given I shutdown Tails and wait for the computer to power off 7.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.996
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.068
And Tor is ready 12.495
Then the Upgrader considers the system as up-to-date 0.116
# 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.924
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.522
After features/support/hooks.rb:331 0.888
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
22.133
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 with a persistent partition enabled and logged in 9.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 11.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.665
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.000