Project Number Date
test_Tails_ISO_devel 4285 16 Mar 2026, 16: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 13:41.405 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:20.571
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.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 15.003
When I start Tails from USB drive "old" with network unplugged 1:0.805
Then the boot device has safe access rights 2.950
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 3.544
After features/support/hooks.rb:100 0.015
Tags: @product
1:30.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 55.691
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 25.667
And I take note of which tps features are available 0.842
Then a Tails persistence partition exists on USB drive "old" 0.699
And I shutdown Tails and wait for the computer to power off 6.957
After features/support/hooks.rb:331 0.641
After features/support/hooks.rb:100 0.011
Tags: @product
1:29.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.748
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.519
When I write some files expected to persist 1.450
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.558
And all persistent directories from the old Tails version have safe access rights 2.194
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 4.122
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.240
After features/support/hooks.rb:331 0.335
After features/support/hooks.rb:100 0.025
Tags: @product
2:17.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.761
And I log in to a new session 12.158
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.032
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.266
Then the running Tails is installed on USB drive "to_upgrade" 17.790
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 2.820
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.766
Then all tps features from the old Tails version are active 0.916
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.225
And all persistent directories from the old Tails version have safe access rights 2.033
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
5:20.522
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 9.424
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.025
And Tor is ready 45.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.478
Given I shutdown Tails and wait for the computer to power off 19.440
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.542
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.236
When the network is plugged 0.014
And Tor is ready 22.432
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.597
Given I shutdown Tails and wait for the computer to power off 18.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.499
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.154
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.189
When the network is plugged 0.019
And Tor is ready 21.138
Then the Upgrader considers the system as up-to-date 0.106
# 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.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.492
After features/support/hooks.rb:331 0.910
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
28.980
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.343
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
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.019
And Tor is ready 19.700
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.465
After features/support/hooks.rb:331 0.756
After features/support/hooks.rb:100 0.000