Project Number Date
test_Tails_ISO_stable 6679 17 Sep 2026, 14:24

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:57.022 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:11.237
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.526
When I start Tails from USB drive "old" with network unplugged 53.578
Then the boot device has safe access rights 2.307
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.839
After features/support/hooks.rb:108 0.016
Tags: @product
1:25.167
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.153
And I start Tails from USB drive "old" with network unplugged and I login 49.635
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.918
And I take note of which tps features are available 6.737
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 3.917
After features/support/hooks.rb:339 0.155
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.295
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.163
Then Tails is running from USB drive "old" 0.235
And all tps features are active 7.601
When I write some files expected to persist 1.733
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.171
And I take note of which tps features are available 7.063
And I shutdown Tails and wait for the computer to power off 4.092
# 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" 12.473
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.009
Tags: @product
2:14.799
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.680
And I log in to a new session 12.209
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.718
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.016
Then the running Tails is installed on USB drive "to_upgrade" 18.691
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 1.798
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.721
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.443
Then all tps features from the old Tails version are active 1.184
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.175
And the expected persistent files created with the old Tails version are present in the filesystem 0.945
And all persistent directories from the old Tails version have safe access rights 1.663
After features/support/hooks.rb:339 0.471
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
3:50.339
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.865
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.024
And Tor is ready 12.327
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 4.633
Given I shutdown Tails and wait for the computer to power off 6.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.090
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.175
When the network is plugged 0.032
And Tor is ready 11.399
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.052
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.832
Given I shutdown Tails and wait for the computer to power off 4.057
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.570
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.677
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.046
And Tor is ready 10.459
Then the Upgrader considers the system as up-to-date 10.448
# 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.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.462
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 7.781
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.150
After features/support/hooks.rb:339 0.720
After features/support/hooks.rb:108 0.000