Project Number Date
test_Tails_ISO_stable 6660 12 Sep 2026, 11:26

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 10:45.511 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:6.338
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.904
When I start Tails from USB drive "old" with network unplugged 49.697
Then the boot device has safe access rights 1.986
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.746
After features/support/hooks.rb:108 0.019
Tags: @product
1:17.121
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.227
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 21.541
And I take note of which tps features are available 5.980
Then a Tails persistence partition exists on USB drive "old" 0.453
And I shutdown Tails and wait for the computer to power off 2.598
After features/support/hooks.rb:339 0.209
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.028
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.525
Then Tails is running from USB drive "old" 0.166
And all tps features are active 6.848
When I write some files expected to persist 1.194
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.285
And all persistent directories from the old Tails version have safe access rights 1.495
And I take note of which tps features are available 5.667
And I shutdown Tails and wait for the computer to power off 2.490
# 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.096
After features/support/hooks.rb:339 0.303
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.147
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.243
And I log in to a new session 10.115
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.609
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.392
Then the running Tails is installed on USB drive "to_upgrade" 17.348
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 0.564
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.176
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.273
Then all tps features from the old Tails version are active 1.069
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 1.972
And the expected persistent files created with the old Tails version are present in the filesystem 0.846
And all persistent directories from the old Tails version have safe access rights 1.711
After features/support/hooks.rb:339 0.469
After features/support/hooks.rb:108 0.006
3:19.450
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.176
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.261
When the network is plugged 0.026
And Tor is ready 11.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.473
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.111
Given I shutdown Tails and wait for the computer to power off 5.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.857
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.535
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
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.139
# 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.200
When the network is plugged 0.047
And Tor is ready 10.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.820
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.486
Given I shutdown Tails and wait for the computer to power off 2.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.018
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.716
And the file system changes introduced in version 6.3~testoverlayfs are present 0.334
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.085
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.060
And Tor is ready 10.118
Then the Upgrader considers the system as up-to-date 0.133
# 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.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.069
19.249
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.821
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 10.186
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.877
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.000