Project Number Date
test_Tails_ISO_devel 4165 14 Jan 2026, 11:49

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 10:44.268 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
59.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.157
When I start Tails from USB drive "old" with network unplugged 41.655
Then the boot device has safe access rights 2.774
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:331 3.784
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 50.921
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.648
And I take note of which tps features are available 0.608
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 7.947
After features/support/hooks.rb:331 0.321
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.587
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.110
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.085
When I write some files expected to persist 1.222
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.787
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 7.903
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.598
After features/support/hooks.rb:331 0.237
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.410
And I log in to a new session 10.020
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.403
Then the running Tails is installed on USB drive "to_upgrade" 15.035
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.110
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.427
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.547
And the expected persistent files created with the old Tails version are present in the filesystem 1.077
And all persistent directories from the old Tails version have safe access rights 1.805
After features/support/hooks.rb:331 0.584
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:24.961
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.938
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
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.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.012
And Tor is ready 12.952
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.308
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.119
Given I shutdown Tails and wait for the computer to power off 6.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.814
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.057
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.018
And Tor is ready 10.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.490
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.789
Given I shutdown Tails and wait for the computer to power off 4.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.799
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.340
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.020
And Tor is ready 10.689
Then the Upgrader considers the system as up-to-date 10.619
# 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 3.746
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 0.881
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.110
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.268
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.273
After features/support/hooks.rb:331 0.596
After features/support/hooks.rb:100 0.000