Project Number Date
test_Tails_ISO_stable 6287 11 Apr 2026, 11:27

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:30.827 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:1.390
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.886
When I start Tails from USB drive "old" with network unplugged 43.181
Then the boot device has safe access rights 2.590
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.707
After features/support/hooks.rb:100 0.026
Tags: @product
1:29.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 54.512
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 24.927
And I take note of which tps features are available 0.713
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 8.645
After features/support/hooks.rb:331 0.196
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.962
Then Tails is running from USB drive "old" 0.294
And all tps features are active 1.307
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 1.763
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 4.242
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.223
After features/support/hooks.rb:331 0.486
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.557
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 without a persistent partition and stopped at Tails Greeter's login screen 7.926
And I log in to a new session 12.891
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.237
Then the running Tails is installed on USB drive "to_upgrade" 15.143
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.103
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.371
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.858
Then all tps features from the old Tails version are active 1.048
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.484
And the expected persistent files created with the old Tails version are present in the filesystem 1.142
And all persistent directories from the old Tails version have safe access rights 2.030
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:43.682
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 with a persistent partition enabled and logged in 8.684
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.500
When the network is plugged 0.017
And Tor is ready 22.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.793
Given I shutdown Tails and wait for the computer to power off 20.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.622
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.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.203
When the network is plugged 0.014
And Tor is ready 22.520
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.177
Given I shutdown Tails and wait for the computer to power off 17.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.425
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.121
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 21.102
Then the Upgrader considers the system as up-to-date 0.100
# 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.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.525
After features/support/hooks.rb:331 0.821
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
28.449
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 7.912
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
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.017
And Tor is ready 19.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.347
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.000