Project Number Date
test_Tails_ISO_stable 6678 17 Sep 2026, 14:00

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 11:41.559 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:13.216
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.427
When I start Tails from USB drive "old" with network unplugged 55.991
Then the boot device has safe access rights 2.045
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.870
After features/support/hooks.rb:108 0.034
Tags: @product
1:25.197
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 50.453
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.153
And I take note of which tps features are available 6.659
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 4.014
After features/support/hooks.rb:339 0.205
After features/support/hooks.rb:108 0.012
Tags: @product
1:37.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.704
Then Tails is running from USB drive "old" 0.230
And all tps features are active 7.109
When I write some files expected to persist 1.107
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.732
And I take note of which tps features are available 7.047
And I shutdown Tails and wait for the computer to power off 5.388
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.537
After features/support/hooks.rb:339 0.340
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.665
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.912
And I log in to a new session 13.687
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.751
And I plug USB drive "to_upgrade" 2.282
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.286
Then the running Tails is installed on USB drive "to_upgrade" 18.481
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.863
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.487
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.829
Then all tps features from the old Tails version are active 1.268
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.443
And the expected persistent files created with the old Tails version are present in the filesystem 0.953
And all persistent directories from the old Tails version have safe access rights 1.688
After features/support/hooks.rb:339 0.697
After features/support/hooks.rb:108 0.066
Tags: @product @automatic_upgrade
3:41.759
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.446
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.033
And Tor is ready 12.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.959
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.305
Given I shutdown Tails and wait for the computer to power off 5.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.306
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.198
When the network is plugged 0.026
And Tor is ready 12.233
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.242
Given I shutdown Tails and wait for the computer to power off 3.966
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.015
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.031
And Tor is ready 10.568
Then the Upgrader considers the system as up-to-date 0.077
# 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 3.650
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.265
After features/support/hooks.rb:339 0.717
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.783
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.811
After features/support/hooks.rb:339 0.949
After features/support/hooks.rb:108 0.000