Project Number Date
test_Tails_ISO_devel 4215 06 Feb 2026, 08:13

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:14.994 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.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.635
When I start Tails from USB drive "old" with network unplugged 41.595
Then the boot device has safe access rights 2.290
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.156
After features/support/hooks.rb:100 0.005
Tags: @product
1:19.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 50.416
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.237
And I take note of which tps features are available 0.697
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 4.078
After features/support/hooks.rb:331 0.647
After features/support/hooks.rb:100 0.006
Tags: @product
1:16.435
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.900
Then Tails is running from USB drive "old" 0.244
And all tps features are active 0.926
When I write some files expected to persist 1.139
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.625
And I take note of which tps features are available 0.196
And I shutdown Tails and wait for the computer to power off 2.743
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.160
After features/support/hooks.rb:331 0.387
After features/support/hooks.rb:100 0.005
Tags: @product
2:16.595
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 7.467
And I log in to a new session 11.848
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.689
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.937
Then the running Tails is installed on USB drive "to_upgrade" 16.129
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:331 3.682
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.352
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.008
Then all tps features from the old Tails version are active 0.907
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.090
And all persistent directories from the old Tails version have safe access rights 1.672
After features/support/hooks.rb:331 0.904
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
3:58.328
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 23.556
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.017
And Tor is ready 12.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.038
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.628
Given I shutdown Tails and wait for the computer to power off 15.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.617
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.043
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
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.123
# 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.238
When the network is plugged 0.021
And Tor is ready 10.630
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.687
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.880
Given I shutdown Tails and wait for the computer to power off 7.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.917
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.099
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.055
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.015
And Tor is ready 10.076
Then the Upgrader considers the system as up-to-date 10.516
# 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.773
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.813
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.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.557
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.274
After features/support/hooks.rb:331 0.913
After features/support/hooks.rb:100 0.000