Project Number Date
test_Tails_ISO_doc-rm-7.12 1 02 Sep 2026, 22:14

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:48.955 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:9.772
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.142
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.118
When I start Tails from USB drive "old" with network unplugged 51.107
Then the boot device has safe access rights 2.680
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.795
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.724
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 51.295
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 23.838
And I take note of which tps features are available 6.698
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 4.050
After features/support/hooks.rb:339 0.163
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.549
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.998
Then Tails is running from USB drive "old" 0.271
And all tps features are active 8.383
When I write some files expected to persist 1.136
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.710
And I take note of which tps features are available 6.286
And I shutdown Tails and wait for the computer to power off 5.194
# 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.005
After features/support/hooks.rb:339 0.293
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.784
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 9.098
And I log in to a new session 12.010
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.972
And I plug USB drive "to_upgrade" 2.342
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.880
Then the running Tails is installed on USB drive "to_upgrade" 19.236
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.946
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.494
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.726
Then all tps features from the old Tails version are active 1.147
And Tails is running from USB drive "to_upgrade" 0.190
And the boot device has safe access rights 2.395
And the expected persistent files created with the old Tails version are present in the filesystem 1.160
And all persistent directories from the old Tails version have safe access rights 1.788
After features/support/hooks.rb:339 0.749
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:44.141
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 8.515
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
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.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.033
And Tor is ready 14.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.922
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.647
Given I shutdown Tails and wait for the computer to power off 7.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.335
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.949
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.265
When the network is plugged 0.032
And Tor is ready 11.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.090
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.722
Given I shutdown Tails and wait for the computer to power off 2.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.789
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.365
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.038
And Tor is ready 10.847
Then the Upgrader considers the system as up-to-date 0.089
# 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.632
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.488
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 8.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.926
After features/support/hooks.rb:339 0.672
After features/support/hooks.rb:108 0.000