Project Number Date
test_Tails_ISO_devel 4153 06 Jan 2026, 08:55

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.663 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:16.760
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.121
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.257
When I start Tails from USB drive "old" with network unplugged 56.337
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:331 3.496
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 56.244
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 24.895
And I take note of which tps features are available 0.837
Then a Tails persistence partition exists on USB drive "old" 0.676
And I shutdown Tails and wait for the computer to power off 8.393
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.064
Then Tails is running from USB drive "old" 0.299
And all tps features are active 1.183
When I write some files expected to persist 1.633
# 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.422
And all persistent directories from the old Tails version have safe access rights 2.446
And I take note of which tps features are available 0.198
And I shutdown Tails and wait for the computer to power off 8.397
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.519
After features/support/hooks.rb:331 0.469
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.071
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 without a persistent partition and stopped at Tails Greeter's login screen 9.031
And I log in to a new session 13.372
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.078
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.987
Then the running Tails is installed on USB drive "to_upgrade" 18.025
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 3.611
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.447
Then all tps features from the old Tails version are active 1.374
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.310
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 2.400
After features/support/hooks.rb:331 0.748
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
3:39.162
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.381
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.571
When the network is plugged 0.025
And Tor is ready 12.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.512
Given I shutdown Tails and wait for the computer to power off 8.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.276
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.474
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.213
When the network is plugged 0.017
And Tor is ready 10.435
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.657
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.507
Given I shutdown Tails and wait for the computer to power off 7.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.779
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.271
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.020
And Tor is ready 10.927
Then the Upgrader considers the system as up-to-date 0.146
# 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.094
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.478
After features/support/hooks.rb:331 0.897
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
20.325
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 7.633
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 11.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 0.888
After features/support/hooks.rb:100 0.000