Project Number Date
test_Tails_ISO_stable 6120 04 Feb 2026, 17:08

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:9.810 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:30.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 27.223
When I start Tails from USB drive "old" with network unplugged 58.507
Then the boot device has safe access rights 2.916
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 1.360
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:2.340
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 28.861
And I take note of which tps features are available 1.152
Then a Tails persistence partition exists on USB drive "old" 0.675
And I shutdown Tails and wait for the computer to power off 3.178
After features/support/hooks.rb:331 0.241
After features/support/hooks.rb:100 0.009
Tags: @product
1:47.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:14.280
Then Tails is running from USB drive "old" 0.287
And all tps features are active 1.871
When I write some files expected to persist 1.543
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.170
And I take note of which tps features are available 0.577
And I shutdown Tails and wait for the computer to power off 7.678
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.013
After features/support/hooks.rb:331 0.411
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.472
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 10.337
And I log in to a new session 9.959
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.542
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.308
Then the running Tails is installed on USB drive "to_upgrade" 19.523
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 1.722
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.616
Then all tps features from the old Tails version are active 1.519
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 3.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.267
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:5.119
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 with a persistent partition enabled and logged in 10.053
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.057
And Tor is ready 12.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.762
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.451
Given I shutdown Tails and wait for the computer to power off 7.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.130
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.225
# 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.252
When the network is plugged 0.047
And Tor is ready 12.998
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.647
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.573
Given I shutdown Tails and wait for the computer to power off 4.752
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.816
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.052
And Tor is ready 11.943
Then the Upgrader considers the system as up-to-date 0.122
# 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.992
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.757
After features/support/hooks.rb:331 1.205
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.127
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.677
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.065
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.057
And Tor is ready 11.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.646
After features/support/hooks.rb:331 1.071
After features/support/hooks.rb:100 0.000