Project Number Date
test_Tails_ISO_devel 4161 10 Jan 2026, 11:43

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:32.790 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
58.914
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.191
When I start Tails from USB drive "old" with network unplugged 40.595
Then the boot device has safe access rights 3.231
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.748
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.520
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 53.062
Then Tails is running from USB drive "old" 0.520
And I create a persistent partition 24.333
And I take note of which tps features are available 0.652
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.313
After features/support/hooks.rb:331 0.382
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.135
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.176
When I write some files expected to persist 1.694
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.029
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 8.408
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.688
After features/support/hooks.rb:331 0.223
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.407
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.203
And I log in to a new session 13.127
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.648
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.762
Then the running Tails is installed on USB drive "to_upgrade" 16.107
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 4.002
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.053
Then all tps features from the old Tails version are active 1.095
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.767
And the expected persistent files created with the old Tails version are present in the filesystem 1.276
And all persistent directories from the old Tails version have safe access rights 1.985
After features/support/hooks.rb:331 0.713
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:53.057
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.256
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.386
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.018
And Tor is ready 13.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.820
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.047
Given I shutdown Tails and wait for the computer to power off 9.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.270
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.237
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.183
When the network is plugged 0.016
And Tor is ready 10.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.665
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.447
Given I shutdown Tails and wait for the computer to power off 4.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.140
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.556
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.057
And Tor is ready 39.398
Then the Upgrader considers the system as up-to-date 0.131
# 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.345
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
20.204
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.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.874
After features/support/hooks.rb:331 1.022
After features/support/hooks.rb:100 0.000