Project Number Date
test_Tails_ISO_devel 4205 03 Feb 2026, 08:55

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:54.317 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:32.706
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 26.882
When I start Tails from USB drive "old" with network unplugged 1:0.852
Then the boot device has safe access rights 2.914
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 1.294
After features/support/hooks.rb:100 0.011
Tags: @product
1:37.829
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 59.567
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 28.435
And I take note of which tps features are available 1.168
Then a Tails persistence partition exists on USB drive "old" 0.676
And I shutdown Tails and wait for the computer to power off 7.476
After features/support/hooks.rb:331 0.631
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.887
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.879
When I write some files expected to persist 1.376
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.063
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 7.372
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.508
After features/support/hooks.rb:331 0.298
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.545
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 without a persistent partition and stopped at Tails Greeter's login screen 9.382
And I log in to a new session 9.434
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.534
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.073
Then the running Tails is installed on USB drive "to_upgrade" 18.179
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 3.774
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.150
Then all tps features from the old Tails version are active 1.323
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.650
And the expected persistent files created with the old Tails version are present in the filesystem 1.310
And all persistent directories from the old Tails version have safe access rights 1.977
After features/support/hooks.rb:331 1.039
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:3.988
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 9.279
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.065
And Tor is ready 13.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.679
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.833
Given I shutdown Tails and wait for the computer to power off 7.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.024
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.842
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.196
When the network is plugged 0.056
And Tor is ready 11.684
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.251
Given I shutdown Tails and wait for the computer to power off 7.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.263
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.016
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.066
And Tor is ready 10.483
Then the Upgrader considers the system as up-to-date 10.628
# 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.207
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.540
After features/support/hooks.rb:331 1.152
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
20.799
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 9.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 9.645
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.702
After features/support/hooks.rb:331 1.093
After features/support/hooks.rb:100 0.000