Project Number Date
test_Tails_ISO_devel 4375 05 May 2026, 11:00

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:54.876 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:0.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.028
When I start Tails from USB drive "old" with network unplugged 43.111
Then the boot device has safe access rights 2.597
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.643
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 52.486
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.158
And I take note of which tps features are available 0.576
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 8.166
After features/support/hooks.rb:331 0.184
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.450
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 with persistence enabled 59.772
Then Tails is running from USB drive "old" 0.269
And all tps features are active 1.109
When I write some files expected to persist 1.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 1.899
And I take note of which tps features are available 0.172
And I shutdown Tails and wait for the computer to power off 2.641
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.740
After features/support/hooks.rb:331 0.383
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.108
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.451
And I log in to a new session 11.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.346
Then the running Tails is installed on USB drive "to_upgrade" 15.566
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 3.584
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.239
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.383
Then all tps features from the old Tails version are active 0.877
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.583
And the expected persistent files created with the old Tails version are present in the filesystem 1.196
And all persistent directories from the old Tails version have safe access rights 1.934
After features/support/hooks.rb:331 0.997
After features/support/hooks.rb:100 0.006
4:26.800
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.353
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.016
And Tor is ready 19.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.656
Given I shutdown Tails and wait for the computer to power off 19.775
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.530
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.140
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.179
When the network is plugged 0.013
And Tor is ready 21.090
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.162
Given I shutdown Tails and wait for the computer to power off 17.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.840
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.089
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.039
And Tor is ready 20.142
Then the Upgrader considers the system as up-to-date 0.115
# 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.149
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.011
24.642
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.234
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.000