Project Number Date
test_Tails_ISO_devel 4173 17 Jan 2026, 08:54

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 13:17.698 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:22.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 28.638
When I start Tails from USB drive "old" with network unplugged 48.903
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:331 4.072
After features/support/hooks.rb:100 0.022
Tags: @product
1:42.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:2.909
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 29.079
And I take note of which tps features are available 1.325
Then a Tails persistence partition exists on USB drive "old" 0.721
And I shutdown Tails and wait for the computer to power off 7.859
After features/support/hooks.rb:331 0.639
After features/support/hooks.rb:100 0.009
Tags: @product
1:52.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.369
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.135
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.747
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 7.817
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.473
After features/support/hooks.rb:331 0.255
After features/support/hooks.rb:100 0.012
Tags: @product
2:26.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.095
And I log in to a new session 9.834
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.150
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.783
Then the running Tails is installed on USB drive "to_upgrade" 19.682
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 3.897
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.405
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.786
Then all tps features from the old Tails version are active 1.452
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 3.114
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 2.180
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.009
4:7.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.708
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.057
And Tor is ready 12.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.591
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.886
Given I shutdown Tails and wait for the computer to power off 7.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.652
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.543
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.262
When the network is plugged 0.064
And Tor is ready 13.225
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.642
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.573
Given I shutdown Tails and wait for the computer to power off 8.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.103
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.260
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.054
And Tor is ready 11.269
Then the Upgrader considers the system as up-to-date 0.149
# 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.952
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.996
After features/support/hooks.rb:331 1.102
After features/support/hooks.rb:100 0.033
22.642
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.464
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
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.071
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 9.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.156
After features/support/hooks.rb:331 0.810
After features/support/hooks.rb:100 0.000