Project Number Date
test_Tails_ISO_devel 4330 09 Apr 2026, 11:03

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 12:18.728 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:0.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.613
When I start Tails from USB drive "old" with network unplugged 42.566
Then the boot device has safe access rights 2.876
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.690
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 53.188
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 24.968
And I take note of which tps features are available 0.655
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 4.085
After features/support/hooks.rb:331 0.508
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.317
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.276
When I write some files expected to persist 1.267
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 1.902
And I take note of which tps features are available 0.171
And I shutdown Tails and wait for the computer to power off 8.002
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.337
After features/support/hooks.rb:331 0.141
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.671
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.956
And I log in to a new session 12.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.746
And I plug USB drive "to_upgrade" 2.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.848
Then the running Tails is installed on USB drive "to_upgrade" 15.929
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:331 2.117
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.279
Then all tps features from the old Tails version are active 1.068
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.242
And all persistent directories from the old Tails version have safe access rights 1.987
After features/support/hooks.rb:331 0.632
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:38.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.708
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.047
And Tor is ready 21.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.458
Given I shutdown Tails and wait for the computer to power off 20.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.762
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.100
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.223
When the network is plugged 0.013
And Tor is ready 20.228
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.434
Given I shutdown Tails and wait for the computer to power off 17.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.556
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.120
And the file system changes introduced in version 6.3~testoverlayfs are present 0.325
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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.013
And Tor is ready 21.085
Then the Upgrader considers the system as up-to-date 0.127
# 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.290
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.522
After features/support/hooks.rb:331 0.797
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
25.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.928
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.054
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 17.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.985
After features/support/hooks.rb:100 0.000