Project Number Date
test_Tails_ISO_devel 4344 14 Apr 2026, 16:42

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:46.949 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:12.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.429
When I start Tails from USB drive "old" with network unplugged 53.207
Then the boot device has safe access rights 2.827
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:331 3.898
After features/support/hooks.rb:100 0.011
Tags: @product
1:23.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 55.584
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.944
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 2.717
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.712
Then Tails is running from USB drive "old" 0.287
And all tps features are active 1.404
When I write some files expected to persist 1.408
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.114
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 4.184
# 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.238
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.342
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 without a persistent partition and stopped at Tails Greeter's login screen 8.170
And I log in to a new session 16.650
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.806
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.019
Then the running Tails is installed on USB drive "to_upgrade" 16.141
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 3.373
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.998
Then all tps features from the old Tails version are active 1.051
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.697
And the expected persistent files created with the old Tails version are present in the filesystem 1.021
And all persistent directories from the old Tails version have safe access rights 1.971
After features/support/hooks.rb:331 0.732
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
4:46.557
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.449
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.022
And Tor is ready 23.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.794
Given I shutdown Tails and wait for the computer to power off 19.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.674
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.176
When the network is plugged 0.015
And Tor is ready 20.634
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.425
Given I shutdown Tails and wait for the computer to power off 17.765
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.071
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.015
And Tor is ready 22.337
Then the Upgrader considers the system as up-to-date 0.167
# 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 5.491
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.547
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.053
Tags: @product @automatic_upgrade
28.236
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.603
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.013
And Tor is ready 19.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 0.961
After features/support/hooks.rb:100 0.000