Project Number Date
test_Tails_ISO_stable 6134 10 Feb 2026, 15: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 11:13.207 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:7.616
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.230
When I start Tails from USB drive "old" with network unplugged 49.780
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.383
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.846
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.522
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.576
And I take note of which tps features are available 0.745
Then a Tails persistence partition exists on USB drive "old" 0.524
And I shutdown Tails and wait for the computer to power off 4.197
After features/support/hooks.rb:331 0.479
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.463
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.125
When I write some files expected to persist 1.407
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 2.146
And I take note of which tps features are available 0.203
And I shutdown Tails and wait for the computer to power off 7.957
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.199
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.121
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 8.573
And I log in to a new session 11.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.951
And I plug USB drive "to_upgrade" 2.288
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.755
Then the running Tails is installed on USB drive "to_upgrade" 16.180
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.152
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.483
Then all tps features from the old Tails version are active 0.987
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 3.045
And the expected persistent files created with the old Tails version are present in the filesystem 1.145
And all persistent directories from the old Tails version have safe access rights 2.011
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:32.371
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.971
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.019
And Tor is ready 13.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.135
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.227
Given I shutdown Tails and wait for the computer to power off 9.800
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.003
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.199
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.210
When the network is plugged 0.015
And Tor is ready 10.635
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.384
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.446
Given I shutdown Tails and wait for the computer to power off 7.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.069
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.628
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.016
And Tor is ready 11.142
Then the Upgrader considers the system as up-to-date 0.123
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:331 1.074
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
22.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.128
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.058
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 11.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.279
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.000