Project Number Date
test_Tails_ISO_devel 4435 07 Jun 2026, 07: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 12:1.581 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:11.720
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 14.144
When I start Tails from USB drive "old" with network unplugged 52.797
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 1.938
After features/support/hooks.rb:104 0.035
Tags: @product
1:29.908
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 55.787
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 25.713
And I take note of which tps features are available 0.422
Then a Tails persistence partition exists on USB drive "old" 0.645
And I shutdown Tails and wait for the computer to power off 7.009
After features/support/hooks.rb:335 0.430
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.383
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.773
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.189
When I write some files expected to persist 1.524
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.214
And I take note of which tps features are available 0.212
And I shutdown Tails and wait for the computer to power off 7.087
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 13.350
After features/support/hooks.rb:335 0.472
After features/support/hooks.rb:104 0.006
Tags: @product
2:16.946
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.123
And I log in to a new session 15.261
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.270
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.936
Then the running Tails is installed on USB drive "to_upgrade" 16.745
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:335 2.609
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.027
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.058
Then all tps features from the old Tails version are active 0.907
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 2.492
And the expected persistent files created with the old Tails version are present in the filesystem 1.216
And all persistent directories from the old Tails version have safe access rights 2.087
After features/support/hooks.rb:335 0.851
After features/support/hooks.rb:104 0.025
Tags: @product @automatic_upgrade
3:54.048
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.730
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.021
And Tor is ready 12.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.998
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.419
Given I shutdown Tails and wait for the computer to power off 7.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.516
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.255
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.016
And Tor is ready 10.246
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.974
Given I shutdown Tails and wait for the computer to power off 8.105
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.053
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.480
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.017
And Tor is ready 10.148
Then the Upgrader considers the system as up-to-date 10.565
# 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.229
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:335 0.941
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
21.546
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.723
After features/support/hooks.rb:335 0.801
After features/support/hooks.rb:104 0.000