Project Number Date
test_Tails_ISO_devel 4615 14 Sep 2026, 12:12

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:25.834 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:11.798
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.903
When I start Tails from USB drive "old" with network unplugged 53.698
Then the boot device has safe access rights 2.471
And Tails is running from USB drive "old" 0.192
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.458
After features/support/hooks.rb:108 0.007
Tags: @product
1:22.850
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 48.083
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 22.827
And I take note of which tps features are available 6.768
Then a Tails persistence partition exists on USB drive "old" 0.606
And I shutdown Tails and wait for the computer to power off 4.238
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.699
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.846
Then Tails is running from USB drive "old" 0.274
And all tps features are active 7.470
When I write some files expected to persist 1.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.771
And I take note of which tps features are available 6.546
And I shutdown Tails and wait for the computer to power off 3.963
# 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.150
After features/support/hooks.rb:339 0.117
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.933
And I log in to a new session 11.248
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.693
And I plug USB drive "to_upgrade" 2.292
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.607
Then the running Tails is installed on USB drive "to_upgrade" 19.187
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.706
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.367
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.841
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.292
And the expected persistent files created with the old Tails version are present in the filesystem 1.024
And all persistent directories from the old Tails version have safe access rights 1.847
After features/support/hooks.rb:339 0.795
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:31.544
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.363
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
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.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.270
When the network is plugged 0.035
And Tor is ready 12.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.123
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.301
Given I shutdown Tails and wait for the computer to power off 5.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.777
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.900
And the file system changes introduced in version 6.2~testoverlayfs are present 0.172
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.084
# 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.190
When the network is plugged 0.028
And Tor is ready 10.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.964
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.832
Given I shutdown Tails and wait for the computer to power off 4.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.208
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.256
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.026
And Tor is ready 10.041
Then the Upgrader considers the system as up-to-date 0.111
# 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.531
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.291
After features/support/hooks.rb:339 0.813
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
19.354
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.028
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.522
After features/support/hooks.rb:339 0.812
After features/support/hooks.rb:108 0.000