Project Number Date
test_Tails_ISO_stable 6697 28 Sep 2026, 16:20

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:17.124 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:5.972
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.727
When I start Tails from USB drive "old" with network unplugged 48.412
Then the boot device has safe access rights 2.134
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.163
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.656
After features/support/hooks.rb:108 0.007
Tags: @product
1:23.111
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 47.806
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 24.064
And I take note of which tps features are available 6.331
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 4.047
After features/support/hooks.rb:339 0.193
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.001
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.875
Then Tails is running from USB drive "old" 0.232
And all tps features are active 7.920
When I write some files expected to persist 1.244
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.231
And all persistent directories from the old Tails version have safe access rights 1.684
And I take note of which tps features are available 6.287
And I shutdown Tails and wait for the computer to power off 2.581
# 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.687
After features/support/hooks.rb:339 0.341
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.727
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 without a persistent partition and stopped at Tails Greeter's login screen 8.407
And I log in to a new session 12.913
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.613
And I plug USB drive "to_upgrade" 2.336
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.500
Then the running Tails is installed on USB drive "to_upgrade" 17.697
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.050
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.893
Then all tps features from the old Tails version are active 1.181
And Tails is running from USB drive "to_upgrade" 0.168
And the boot device has safe access rights 2.126
And the expected persistent files created with the old Tails version are present in the filesystem 0.923
And all persistent directories from the old Tails version have safe access rights 1.653
After features/support/hooks.rb:339 0.555
After features/support/hooks.rb:108 0.090
3:36.129
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.869
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.037
And Tor is ready 12.236
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.457
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.408
Given I shutdown Tails and wait for the computer to power off 5.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.526
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.049
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.184
When the network is plugged 0.035
And Tor is ready 10.951
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.954
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.659
Given I shutdown Tails and wait for the computer to power off 4.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.178
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.826
And the file system changes introduced in version 6.3~testoverlayfs are present 0.314
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.033
And Tor is ready 10.755
Then the Upgrader considers the system as up-to-date 0.098
# 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.642
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.009
19.131
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.911
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 9.896
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.948
After features/support/hooks.rb:339 0.606
After features/support/hooks.rb:108 0.000