Project Number Date
test_Tails_ISO_devel 4378 05 May 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 11:57.419 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
58.477
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.665
When I start Tails from USB drive "old" with network unplugged 40.414
Then the boot device has safe access rights 2.659
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 1.270
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 53.676
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 24.398
And I take note of which tps features are available 0.689
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 8.072
After features/support/hooks.rb:331 0.644
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.760
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.177
When I write some files expected to persist 1.289
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.534
And all persistent directories from the old Tails version have safe access rights 2.110
And I take note of which tps features are available 0.199
And I shutdown Tails and wait for the computer to power off 8.332
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.635
After features/support/hooks.rb:331 0.249
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.793
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.991
And I log in to a new session 12.508
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.786
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.238
Then the running Tails is installed on USB drive "to_upgrade" 14.719
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.162
After features/support/hooks.rb:331 2.051
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.891
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.108
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.455
And the expected persistent files created with the old Tails version are present in the filesystem 1.066
And all persistent directories from the old Tails version have safe access rights 1.882
After features/support/hooks.rb:331 0.911
After features/support/hooks.rb:100 0.006
4:18.688
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.067
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.021
And Tor is ready 19.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.731
Given I shutdown Tails and wait for the computer to power off 6.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.225
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.192
When the network is plugged 0.017
And Tor is ready 21.309
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.357
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.354
Given I shutdown Tails and wait for the computer to power off 17.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.940
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.114
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.018
And Tor is ready 23.273
Then the Upgrader considers the system as up-to-date 0.087
# 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.519
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.451
After features/support/hooks.rb:331 0.739
After features/support/hooks.rb:100 0.010
25.099
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.340
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 17.025
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.637
After features/support/hooks.rb:100 0.000