Project Number Date
test_Tails_ISO_stable 6197 12 Mar 2026, 14:37

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 13:20.467 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:25.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.014
When I start Tails from USB drive "old" with network unplugged 1:6.438
Then the boot device has safe access rights 3.059
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:331 1.595
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.635
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 56.641
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 25.037
And I take note of which tps features are available 0.785
Then a Tails persistence partition exists on USB drive "old" 0.684
And I shutdown Tails and wait for the computer to power off 4.147
After features/support/hooks.rb:331 0.242
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.806
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.379
When I write some files expected to persist 1.372
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.037
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 8.116
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.670
After features/support/hooks.rb:331 0.286
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.133
And I log in to a new session 10.342
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.961
And I plug USB drive "to_upgrade" 2.307
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.611
Then the running Tails is installed on USB drive "to_upgrade" 17.070
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 2.326
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.163
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.365
Then all tps features from the old Tails version are active 1.010
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.002
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 2.179
After features/support/hooks.rb:331 0.577
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:3.292
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 8.430
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.017
And Tor is ready 22.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.962
Given I shutdown Tails and wait for the computer to power off 14.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.324
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.187
When the network is plugged 0.018
And Tor is ready 21.897
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.893
Given I shutdown Tails and wait for the computer to power off 17.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.124
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
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.211
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.015
And Tor is ready 39.709
Then the Upgrader considers the system as up-to-date 0.104
# 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 5.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:331 0.720
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
26.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 18.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 1.042
After features/support/hooks.rb:100 0.000