Project Number Date
test_Tails_ISO_devel 4328 08 Apr 2026, 11:26

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:52.039 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:5.663
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
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" 14.190
When I start Tails from USB drive "old" with network unplugged 46.719
Then the boot device has safe access rights 2.926
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:331 3.554
After features/support/hooks.rb:100 0.016
Tags: @product
1:28.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 55.922
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 24.032
And I take note of which tps features are available 0.763
Then a Tails persistence partition exists on USB drive "old" 0.666
And I shutdown Tails and wait for the computer to power off 6.956
After features/support/hooks.rb:331 0.206
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.808
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.143
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.071
When I write some files expected to persist 1.443
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.001
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 8.267
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.690
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.392
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 without a persistent partition and stopped at Tails Greeter's login screen 8.454
And I log in to a new session 17.538
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.828
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.780
Then the running Tails is installed on USB drive "to_upgrade" 16.304
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 3.127
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.059
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.869
Then all tps features from the old Tails version are active 1.048
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.744
And the expected persistent files created with the old Tails version are present in the filesystem 1.135
And all persistent directories from the old Tails version have safe access rights 1.960
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:49.627
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.544
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.023
And Tor is ready 23.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.476
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.868
Given I shutdown Tails and wait for the computer to power off 21.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.771
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.214
When the network is plugged 0.015
And Tor is ready 20.616
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.419
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.997
Given I shutdown Tails and wait for the computer to power off 17.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.804
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.404
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.013
And Tor is ready 21.395
Then the Upgrader considers the system as up-to-date 0.187
# 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.913
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:331 1.034
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
26.795
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 7.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 18.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.000