Project Number Date
test_Tails_ISO_stable 6508 16 Jul 2026, 11:32

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:35.082 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:7.095
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.071
When I start Tails from USB drive "old" with network unplugged 50.108
Then the boot device has safe access rights 2.171
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 1.197
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.193
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.220
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.168
And I take note of which tps features are available 3.711
Then a Tails persistence partition exists on USB drive "old" 0.464
And I shutdown Tails and wait for the computer to power off 8.339
After features/support/hooks.rb:339 0.149
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.845
Then Tails is running from USB drive "old" 0.224
And all tps features are active 4.677
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 1.803
And I take note of which tps features are available 3.772
And I shutdown Tails and wait for the computer to power off 3.972
# 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.667
After features/support/hooks.rb:339 0.203
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.258
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 7.686
And I log in to a new session 12.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.343
Then the running Tails is installed on USB drive "to_upgrade" 14.443
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 2.082
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.029
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.535
Then all tps features from the old Tails version are active 0.947
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.072
And all persistent directories from the old Tails version have safe access rights 1.760
After features/support/hooks.rb:339 0.754
After features/support/hooks.rb:108 0.006
3:50.148
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.876
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.013
And Tor is ready 13.132
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.685
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.566
Given I shutdown Tails and wait for the computer to power off 9.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.091
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.195
When the network is plugged 0.031
And Tor is ready 9.932
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.998
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.396
Given I shutdown Tails and wait for the computer to power off 7.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.011
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 4.649
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
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.207
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.017
And Tor is ready 11.037
Then the Upgrader considers the system as up-to-date 10.495
# 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.088
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.010
19.731
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.557
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 8.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.157
After features/support/hooks.rb:339 1.032
After features/support/hooks.rb:108 0.000