Project Number Date
test_Tails_ISO_devel 4249 23 Feb 2026, 23:34

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 12:30.531 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:10.100
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.585
When I start Tails from USB drive "old" with network unplugged 50.180
Then the boot device has safe access rights 3.308
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:331 1.391
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login 54.710
Then Tails is running from USB drive "old" 0.461
And I create a persistent partition 24.596
And I take note of which tps features are available 0.781
Then a Tails persistence partition exists on USB drive "old" 0.589
And I shutdown Tails and wait for the computer to power off 8.254
After features/support/hooks.rb:331 0.420
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.889
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.527
Then Tails is running from USB drive "old" 0.383
And all tps features are active 1.268
When I write some files expected to persist 1.306
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.087
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 4.009
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.485
After features/support/hooks.rb:331 0.479
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.603
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.464
And I log in to a new session 10.069
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.874
And I plug USB drive "to_upgrade" 2.277
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.738
Then the running Tails is installed on USB drive "to_upgrade" 15.872
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 3.572
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.412
Then all tps features from the old Tails version are active 1.178
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.625
And the expected persistent files created with the old Tails version are present in the filesystem 1.201
And all persistent directories from the old Tails version have safe access rights 2.074
After features/support/hooks.rb:331 0.940
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:34.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.138
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.460
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.018
And Tor is ready 21.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.159
Given I shutdown Tails and wait for the computer to power off 20.902
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.633
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.287
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.222
When the network is plugged 0.015
And Tor is ready 20.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.445
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.746
Given I shutdown Tails and wait for the computer to power off 13.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.616
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.016
And Tor is ready 21.080
Then the Upgrader considers the system as up-to-date 0.119
# 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 4.851
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
25.975
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 7.780
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 17.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.508
After features/support/hooks.rb:331 0.784
After features/support/hooks.rb:100 0.000