Project Number Date
test_Tails_ISO_devel 4397 15 May 2026, 11:11

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:5.192 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:12.776
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.736
When I start Tails from USB drive "old" with network unplugged 52.851
Then the boot device has safe access rights 3.215
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:335 3.894
After features/support/hooks.rb:104 0.010
Tags: @product
1:34.286
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.124
And I start Tails from USB drive "old" with network unplugged and I login 58.784
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 25.483
And I take note of which tps features are available 0.460
Then a Tails persistence partition exists on USB drive "old" 0.674
And I shutdown Tails and wait for the computer to power off 8.450
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.007
Tags: @product
1:33.798
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.885
Then Tails is running from USB drive "old" 0.288
And all tps features are active 1.349
When I write some files expected to persist 1.395
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.129
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 8.060
# 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.900
After features/support/hooks.rb:335 0.567
After features/support/hooks.rb:104 0.009
Tags: @product
2:14.070
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.171
And I log in to a new session 13.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.770
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.317
Then the running Tails is installed on USB drive "to_upgrade" 16.998
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:335 3.773
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.225
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.595
Then all tps features from the old Tails version are active 1.175
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.214
And the expected persistent files created with the old Tails version are present in the filesystem 1.512
And all persistent directories from the old Tails version have safe access rights 2.352
After features/support/hooks.rb:335 0.636
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:53.385
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.732
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.014
And Tor is ready 14.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.003
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.245
Given I shutdown Tails and wait for the computer to power off 9.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.244
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.260
When the network is plugged 0.015
And Tor is ready 11.793
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.230
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.808
Given I shutdown Tails and wait for the computer to power off 4.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.851
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.016
And Tor is ready 10.505
Then the Upgrader considers the system as up-to-date 10.550
# 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.303
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:335 1.068
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
22.650
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.955
After features/support/hooks.rb:335 0.622
After features/support/hooks.rb:104 0.000